touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #60911
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
It started failing around Feb 27. It roughly coincides with
https://launchpad.net/ubuntu/+source/glibc/2.19-15ubuntu2 (but that
looks unlikely), the most likely candidate is the upgrade of linux from
3.18 to 3.19: https://launchpad.net/ubuntu/+source/linux/3.19.0-7.7
** 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).
+ 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.
--
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
References