quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: upstart (Ubuntu Quantal)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: upstart (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications about
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Confirmed
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Status: Confirmed => Fix Released
--
You received this bug no
@James -- ok I can trigger this error from the test program as well on
amd64. However after some poking I think this test case is flawed. I
made the read retry if it did not see a 14 long string and in the tests
I have run all failures show the newline is there:
loop 39225 of 9
ret =
** Changed in: linux (Ubuntu Quantal)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications ab
@Brad - logs attached, but note that this problem is not unique to my
system as it can be seen on i386 and ARM systems. It also potentially
affects all precise kernels I believe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3951 F pulseaudio
/dev/snd/controlC0: james 3951 F pulseaudio
/dev/snd/pcmC0D0c: james 3951 F...m pulseaudio
/dev/snd/pcmC0D0p: james 3
** Changed in: linux (Ubuntu Quantal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications about th
Interestingly, I tried running the test program on FreeBSD, but that
fails. I believe the reason is that on BSD, if the process connected to
the master end of the pty has unflushed data that the slave end hasn't
yet read, and the master process is killed, the kernel discards the
unflushed data and
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications abo
After compiling (need to link with -lutil as shown at top of file),
either run with no params, or pass a number which is the number of times
it will run the test:
$ ./bug-1066351
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Attachment added: "test program that demonstrates failure seen in Upstart
tests"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1066351/+attachment/3401404/+files/bug-1066351.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Also now seen intermittently on i386:
loop 174 of
ERROR: incorrect output: result_string='hello, world
', buffer='hello, world'
result_string:
6865 6c6c 6f2c 2077 6f72 6c64 0d0a
hello, world\r\n
buffer:
6865 6c6c 6f2c 2077 6f72 6c64
hello, world
--
You received this bug notification becau
I have just recreated this bug on arm using a test program completely
unrelated to Upstart and NIH:
loop 2926 of
loop 2927 of
loop 2928 of
loop 2929 of
ERROR: incorrect output: result_string='hello, world
', buffer='hello, world'
result_string:
6865 6c6c 6f2c 2077 6f72 6c64 0d0
** Changed in: upstart (Ubuntu Quantal)
Milestone: None => quantal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications
package did now build on the buildds. maybe investigate while it's
locally reproducible?
** Changed in: upstart (Ubuntu Quantal)
Milestone: ubuntu-12.10 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Hi Matthias - this is the issue we have seen before where a rebuild will
probably work. However, I'll see if I can identify what is going on
here...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106635
ah, gotcha. build failure confirmed locally, anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications about this bug go to:
htt
and even if the ftbfs was for a test rebuild ... all these are done on
non-virtual buildds for a reason
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
this has nothing to do with test rebuilds, it's a regular update to
-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
To manage notifications
Is it possible that this bug is specific to the virtual builders used
for the rebuild test? The upstart test suite seems to be very finicky
with regards to kernel versions, and has never had problems building on
the real buildds.
--
You received this bug notification because you are a member of
21 matches
Mail list logo
