touch-packages team mailing list archive

[James Hunt <james.hunt@xxxxxxxxxxxxx>]

Updating the amd64 system, I see the failure on the 2nd test run.

The Upstart logging code doesn't seem to be the culprit fwics meaning
the most likely area is the pty-handling code (either in upstart or in
the kernel).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions