Bug#746925: glib2.0 FTBFS on alpha: test-suite failure in async-splice-output-stream

[Michael Cree]

On Sun, May 04, 2014 at 05:03:42PM +0200, Emilio Pozuelo Monfort wrote:
> > 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.
> 
> Are you sure that this commit is the culprit? 

Bah, not any longer.

> 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.

Despite rerunning the test with and without that commit at the time and
getting results consistent with the above being the problematic commit,
the first time I reran it today proved my hypothesis false.  It now
appears that there is about a 40% to 50% chance of the test suite failing
even without the Serb. transl. commit.

I will have to redo the bisection.

Is there a way to run an individual test?  At the moment I just run 'make
check' but it would be much quicker to bisect if I could run an
individual test. 

Cheers
Michael.