Ok, after a lot of testing and reading of the traces we are seeing a
spurious EIO reported to the read at the end of the file. This in
combination with the way nih handles IO means we lose the last buffer of
the file at times. From the strace log:
1396 read(17, 0x7f78214c3b30, 4096)= -1
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: test_job_process fails in majority of cases
To manage
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: linux (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Andy Whitcroft (
** Changed in: upstart (Ubuntu Vivid)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: test_job_process fails in majority o
Some quick tests suggest that this issue only seems to affect long runs
of nul bytes (even if they are terminated by visible chars + a '\n').
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Titl
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
Updating the amd64 system, I see the failure on the 2nd test run.
The Upstart logging code doesn't seem to be the culprit fwics meaning
the most likely area is the pty-handling code (either in upstart or in
the kernel).
--
You received this bug notification because you are a member of Ubuntu
Bug
It does indeed seem to be related to the kernel. I've just run that
specific test 77 times on an amd64 system running a 3.18.0-11 kernel
with no failures. Once the broken deps issue is resolved, I'll retest on
the same system running the latest 3.19 kernel.
--
You received this bug notification b
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
mk-sbuild now fails with a different error:
Setting up udev (219-4ubuntu3) ...
A chroot environment has been detected, udev not started.
/var/lib/dpkg/info/udev.postinst: 35: /var/lib/dpkg/info/udev.postinst:
update-initramfs: not found
dpkg: error processing package udev (--configure):
subproce
@James: that was due to a set of priority mismatches, these got fixed
now. Try again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: test_job_process fails in majority of cases
'mk-sbuild vivid' currently gives an error:
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
systemd-sysv : Conflicts: upstart but 1.13.2-0ubuntu9 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or sp
This is also reproducible on a package build in sbuild locally.
** Summary changed:
- test_job_process fails in majority of cases
+ FTBFS: test_job_process fails in majority of cases
** Also affects: upstart (Ubuntu Vivid)
Importance: High
Status: New
** Tags added: autopkgtset qa-dai
13 matches
Mail list logo
