On 20/04/12 at 10:17 +0100, Simon McVittie wrote: > >> /stream-tube/offer/race/room/unix/localhost: OK > >> Alarm clock > >> /stream-tube/offer/race/room/unix/credentials: FAIL: test-stream-tube > > This test timed out; either the buildd was too slow/busy, the test has a > race condition, or the library has a race condition. > > How fast are your buildds, how many cores do they have, and how much > else is the same machine doing at the same time? > > In the debian-experimental git branch I've turned off the timeout (to be > nice to sh4 and Ubuntu), so the only timeout will be the buildds' usual > "n minutes with no stdout/stderr"; so if it's that, it'll be fixed soon. > > If it's a race condition, telepathy-glib 0.18 (currently in > experimental, but should probably hit unstable soon) might improve matters. > > It might be <https://bugs.freedesktop.org/show_bug.cgi?id=45173> (which > was a race condition in that test), but that bug was a response to > 139a0f63b6d (fdo#44825, 0.17.4) which isn't in 0.16 either. (It's > possible that the test was always broken and we just didn't catch it > until then, though.)
Hi, It's very likely that it's caused by other load on the buildd. I haven't had time to implement a clean solution to those problems (by redoing failed builds on an idle machine, for example). Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
