kernel-packages team mailing list archive

[Andy Whitcroft <apw@xxxxxxxxxxxxx>]

** Description changed:

  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.
+ 
+ ===
+ break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 1a48632ffed61352a7810ce089dc5a8bcd505a60

** Tags added: kernel-bug-break-fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1429756

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  Invalid

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.

  ===
  break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 1a48632ffed61352a7810ce089dc5a8bcd505a60

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