| 2015-03-09 08:47:12 |
Martin Pitt |
bug |
|
|
added bug |
| 2015-03-09 08:47:20 |
Martin Pitt |
upstart (Ubuntu): importance |
Undecided |
High |
|
| 2015-03-09 08:53:17 |
Martin Pitt |
summary |
test_job_process fails in majority of cases |
FTBFS: test_job_process fails in majority of cases |
|
| 2015-03-09 08:53:22 |
Martin Pitt |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-03-09 08:53:22 |
Martin Pitt |
bug task added |
|
upstart (Ubuntu Vivid) |
|
| 2015-03-09 08:55:51 |
Martin Pitt |
tags |
|
autopkgtset qa-daily-testing |
|
| 2015-03-09 08:55:55 |
Martin Pitt |
tags |
autopkgtset qa-daily-testing |
autopkgtest qa-daily-testing |
|
| 2015-03-09 11:15:01 |
Martin Pitt |
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. |
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. |
|
| 2015-03-10 14:44:33 |
James Hunt |
upstart (Ubuntu Vivid): assignee |
|
James Hunt (jamesodhunt) |
|
| 2015-03-12 15:17:27 |
Andy Whitcroft |
bug task added |
|
linux (Ubuntu) |
|
| 2015-03-12 15:17:36 |
Andy Whitcroft |
linux (Ubuntu Vivid): importance |
Undecided |
High |
|
| 2015-03-12 15:17:41 |
Andy Whitcroft |
linux (Ubuntu Vivid): status |
New |
Confirmed |
|
| 2015-03-12 15:17:44 |
Andy Whitcroft |
linux (Ubuntu Vivid): assignee |
|
Andy Whitcroft (apw) |
|
| 2015-03-12 15:17:47 |
Andy Whitcroft |
linux (Ubuntu Vivid): milestone |
|
ubuntu-15.03 |
|
| 2015-03-12 23:08:37 |
Andy Whitcroft |
linux (Ubuntu Vivid): status |
Confirmed |
In Progress |
|
| 2015-03-12 23:15:50 |
Andy Whitcroft |
summary |
FTBFS: test_job_process fails in majority of cases |
FTBFS: upstart test_job_process fails in majority of cases |
|
| 2015-03-12 23:16:25 |
Andy Whitcroft |
summary |
FTBFS: upstart test_job_process fails in majority of cases |
FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file |
|
| 2015-03-13 09:13:10 |
James Hunt |
attachment added |
|
bug-1429756.tgz https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+attachment/4343995/+files/bug-1429756.tgz |
|
| 2015-03-13 10:26:47 |
James Hunt |
upstart (Ubuntu Vivid): status |
New |
Invalid |
|
| 2015-03-13 10:28:53 |
James Hunt |
summary |
FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file |
FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file |
|
| 2015-03-13 10:40:48 |
James Hunt |
bug |
|
|
added subscriber James Hunt |
| 2015-05-18 14:19:50 |
Andy Whitcroft |
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. |
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 |
|
| 2015-05-18 14:19:58 |
Andy Whitcroft |
tags |
autopkgtest qa-daily-testing |
autopkgtest kernel-bug-break-fix qa-daily-testing |
|
| 2015-05-18 14:45:48 |
Andy Whitcroft |
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 |
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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 |
|
| 2015-05-18 15:39:37 |
Andy Whitcroft |
linux (Ubuntu Vivid): status |
In Progress |
Confirmed |
|
| 2015-05-18 15:39:41 |
Andy Whitcroft |
linux (Ubuntu): status |
In Progress |
Confirmed |
|
| 2015-07-07 03:24:28 |
Launchpad Janitor |
linux (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2015-07-09 15:15:54 |
Brad Figg |
tags |
autopkgtest kernel-bug-break-fix qa-daily-testing |
autopkgtest kernel-bug-break-fix qa-daily-testing verification-needed-vivid |
|
| 2015-07-21 14:49:04 |
Brad Figg |
tags |
autopkgtest kernel-bug-break-fix qa-daily-testing verification-needed-vivid |
autopkgtest kernel-bug-break-fix qa-daily-testing verification-done-vivid |
|
| 2015-07-22 15:38:53 |
Launchpad Janitor |
linux (Ubuntu Vivid): status |
Confirmed |
Fix Released |
|
| 2015-07-23 15:22:22 |
Andy Whitcroft |
tags |
autopkgtest kernel-bug-break-fix qa-daily-testing verification-done-vivid |
autopkgtest qa-daily-testing verification-done-vivid |
|
