Hi, On 04/05/14 02:38, Michael Cree wrote: > Source: glib2.0 > Version: 2.40.0-3 > Severity: important > User: debian-al...@lists.debian.org > Usertags: alpha > Justification: Fails to build from source but built in the past. > > glib2.0 FTBFS on alpha due to the following test-suite error: > > PASS: async-splice-output-stream 1 /async-splice/copy-chunks > PASS: async-splice-output-stream 2 /async-splice/copy-chunks-threaded-input > ERROR: async-splice-output-stream - missing test plan > ERROR: async-splice-output-stream - exited with status 133 (terminated by > signal 5?) > > Full build log at: > http://buildd.debian-ports.org/status/fetch.php?pkg=glib2.0&arch=alpha&ver=2.40.0-3&stamp=1398626766 > > I bisected with upstream source from a working version to find that commit > be25603b947876f13ab7d9cee6a8c367f8f528ff (Updated Serbian translation) is > the offending commit !!!! Indeed, removing this commit from Debian source > version 2.40.0-3 results in glib2.0 building to completion on Alpha.
I suppose you / the buildd aren't running with a serbian locale? Are you sure that this commit is the culprit? I would rather guess that the test is intermittently failing (e.g. because of a race condition), and that it randomly passed after you reverted that commit while it randomly failed with that commit applied. Please run the test in a loop and see if it consistently fails with that commit and if it consistently passes without it. Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
