touch-packages team mailing list archive

[James Hunt <james.hunt@xxxxxxxxxxxxx>]

The "good" news is that this test failure is a real bug: running 1024
job instances of what is effectively the failing tests shows...

- 3.18 kernel: 0 job instances have incorrect size.
- 3.19 kernel: 848 job instances have the **incorrect** size (!!)

Figures are from a fully-updated amd64 vivid system booted to use
Upstart and simply toggling the kernel being used.

I've tried to recreate the failure using script(1) and dd(1), but so far
this has proven unsuccessful.

-- 
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