[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** Tags removed: 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: Fix Released Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Released 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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
This bug was fixed in the package linux - 3.19.0-23.24
---
linux (3.19.0-23.24) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1472346
[ Chris J Arges ]
* SAUCE: Don't use atomic read in evlist.c
- LP: #1410673
linux (3.19.0-23.23) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1472048
[ Chris J Arges ]
* [Config] Add CRYPTO_DEV_NX_*, 842_* as modules
- LP: #1454687
[ Lu, Han ]
* SAUCE: i915_bpo: drm/i915/audio: add codec wakeup override
enabled/disable callback
- LP: #1460674
[ Timo Aaltonen ]
* SAUCE: Backport I915_OVERLAY_DISABLE_DEST_COLORKEY
- LP: #1460674
* SAUCE: i915_bpo: Rebase to drm-intel-next-fixes-2015-05-29
- LP: #1460674
* SAUCE: i915_bpo: Revert drm/i915: Implement the intel_dp_autotest_edid
function for DP EDID complaince tests
- LP: #1460674
* SAUCE: i915_bpo: Revert drm/i915: Add debugfs test control files for
Displayport compliance testing
- LP: #1460674
* SAUCE: Load i915_bpo from the hda driver on SKL/CHV
- LP: #1460674
* SAUCE: i915_bpo: Don't try to support BXT
- LP: #1460674
* SAUCE: i915_bpo: drm/i915/skl: Fix DMC API version.
[ Upstream Kernel Changes ]
* Revert usb: dwc2: add bus suspend/resume for dwc2
- LP: #1471252
* Revert HID: logitech-hidpp: support combo keyboard touchpad TK820
- LP: #1471252
* Revert KVM: x86: drop fpu_activate hook
- LP: #1471252
* Revert libceph: clear r_req_lru_item in __unregister_linger_request()
- LP: #1471252
* drm/i915: add component support
- LP: #1460661
* ALSA: hda: export struct hda_intel
- LP: #1460661
* ALSA: hda: pass intel_hda to all i915 interface functions
- LP: #1460661
* ALSA: hda: add component support
- LP: #1460661
* drm/atomic-helpers: Fix documentation typos and wrong copypaste
- LP: #1460674
* drm/atomic: Rename drm_atomic_helper_commit_pre_planes() state argument
- LP: #1460674
* drm/atomic-helper: Rename commmit_post/pre_planes
- LP: #1460674
* drm/atomic-helpers: make mode_set hooks optional
- LP: #1460674
* drm/atomic-helper: Fix kerneldoc for prepare_planes
- LP: #1460674
* drm: Complete moving rotation property to core
- LP: #1460674
* drm: Share plane pixel format check code between legacy and atomic
- LP: #1460674
* drm/atomic: Constify a bunch of functions pointer structs
- LP: #1460674
* drm: Fix some typo mistake of the annotations
- LP: #1460674
* drm: change connector to tmp_connector
- LP: #1460674
* drm: atomic: Expose CRTC active property
- LP: #1460674
* drm: atomic: Allow setting CRTC active property
- LP: #1460674
* drm/atomic-helpers: Properly avoid full modeset dance
- LP: #1460674
* drm/atomic: Add helpers for state-subclassing drivers
- LP: #1460674
* drm: Fix some typos
- LP: #1460674
* drm/atomic: Add for_each_{connector,crtc,plane}_in_state helper macros
- LP: #1460674
* drm/atomic-helper: Don't call atomic_update_plane when it stays off
- LP: #1460674
* drm/atomic-helper: Really recover pre-atomic plane/cursor behavior
- LP: #1460674
* drm/atomic: Make mode_fixup() optional for check_modeset()
- LP: #1460674
* drm/atomic-helpers: Update vblank timestamping constants
- LP: #1460674
* drm/atomic-helpers: Export
drm_atomic_helper_update_legacy_modeset_state
- LP: #1460674
* drm/atomic: add drm_atomic_get_existing_*_state helpers
- LP: #1460674
* drm/atomic: remove duplicated assignment of old_plane_state
- LP: #1460674
* drm/atomic: Allow drivers to subclass drm_atomic_state, v3
- LP: #1460674
* drm/dp: indentation and ordering cleanups
- LP: #1460674
* drm/dp: add DPCD definitions from eDP 1.2
- LP: #1460674
* drm/dp: add DPCD definitions from DP 1.1 and 1.2a
- LP: #1460674
* drm/dp: add DPCD definitions from eDP 1.4
- LP: #1460674
* drm: Adding drm helper function drm_plane_from_index().
- LP: #1460674
* ALSA: hda - reset display codec when power on
- LP: #1460674
* drm/i915/audio: add codec wakeup override enabled/disable callback
- LP: #1460674
* scsi: storvsc: Increase the ring buffer size
- LP: #1445195
* scsi: storvsc: Size the queue depth based on the ringbuffer size
- LP: #1445195
* scsi: storvsc: Always send on the selected outgoing channel
- LP: #1445195
* scsi: storvsc: Retrieve information about the capability of the target
- LP: #1445195
* scsi: storvsc: Don't assume that the scatterlist is not chained
- LP: #1445195
* scsi: storvsc: Set the tablesize based on the information given by the
host
- LP: #1445195
* Drivers: hv: vmbus: Add support for VMBus panic notifier handler
- LP: #1463584
* Drivers: hv: vmbus: Correcting truncation error for constant
HV_CRASH_CTL_CRASH_NOTIFY
- LP: #1463584
* net: eth: xgene: change APM X-Gene SoC platform
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- 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: Fix Released Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed 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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- 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: Fix Released Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed 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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
This bug was fixed in the package linux - 4.0.0-4.6 --- linux (4.0.0-4.6) wily; urgency=low [ Andy Whitcroft ] * Release Tracking Bug - LP: #1470233 * rebase to mainline v4.0.7 [ Jay Vosburgh ] * SAUCE: fan: Proof of concept implementation (v2) - LP: #1439706 * SAUCE: fan: tunnel multiple mapping mode (v3) - LP: #1470091 [ Upstream Kernel Changes ] * rebase to v4.0.7 - LP: #1427680 - LP: #1462614 -- Andy Whitcroft a...@canonical.com Tue, 30 Jun 2015 16:55:32 +0100 ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released -- 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: Fix Released Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed 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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** 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 + break-fix: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 -- 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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** Changed in: linux (Ubuntu Vivid) Status: In Progress = Confirmed ** Changed in: linux (Ubuntu) Status: In Progress = Confirmed -- 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: Confirmed Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed 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: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
Hi Andy - any progress on this? Although the buildd's are running older kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and is thus causing upstart tests to fail. For example: https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt- upstart/ARCH=amd64,label=adt/lastBuild/ If it will take a while to resolve this, I guess we'll have to consider disabling the test for now. However, doing so is going to change the behaviour of the upstart logger. -- 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
