[Bug 1256947] Re: Incorrect use of context managers causes FTBFS on buildds

[Barry Warsaw]

Michael Foord identified the problem.  I am incorrectly interleaving
unittest.mock.patch calls which get unwound in the wrong order.  On
local builds, the tests are run in an order which does not trigger this
problem, but I guess fortunately, the buildds run the tests in a
different order and the problem becomes evident.  Fortunately, it's an
easy fix - don't interleave the patch calls.


** Summary changed:

- FTBFS on buildds
+ Incorrect use of context managers causes FTBFS on buildds

** Also affects: ubuntu-system-image
   Importance: Undecided
       Status: New

** Changed in: ubuntu-system-image
       Status: New => In Progress

** Changed in: ubuntu-system-image
   Importance: Undecided => Critical

** Changed in: ubuntu-system-image
     Assignee: (unassigned) => Barry Warsaw (barry)

** Tags added: client

** Changed in: ubuntu-system-image
    Milestone: None => 2.0.2

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1256947

Title:
  Incorrect use of context managers causes FTBFS on buildds

Status in Ubuntu system image (server/client/updater):
  In Progress
Status in “system-image” package in Ubuntu:
  In Progress

Bug description:
  2.0 is FTBFS on trusty-proposed due to test suite failures that are
  unreproducible in local sbuilds.  The test failure occurs both on the
  main buildd and in ppas:

  https://launchpad.net/ubuntu/+source/system-
  image/2.0.1-0ubuntu1/+build/5275242

  Currently working on some PPA builds with quilt patches to help debug
  the problem.  Due to PPA turnaround time, this will be slow going.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1256947/+subscriptions