Re: Testsuite failures on Ubuntu's autobuilders

[bojo42]

As PSPP finally migrated to testing in Debian now, i uploaded the new
version to mentors. Please push it Ben.

Cheers

Am Mittwoch, den 21.03.2012, 10:15 +0100 schrieb bojo42:
> John's fix works:
> https://launchpadlibrarian.net/97611171/buildlog_ubuntu-precise-i386.pspp_0.7.9%2Bgit20120319-0ubuntu1~bojo1~precise1_BUILDING.txt.gz
> 
> Thanks.
> 
> Am Sonntag, den 18.03.2012, 14:29 -0700 schrieb Ben Pfaff:
> > I haven't done anything to address that one yet, and I don't
> > think that John has either.
> > 
> > bojo42 <address@hidden> writes:
> > 
> > > I let it rebuild for precise with current Git and while the 180 & 181
> > > are fixed just fine, there still is an error with the 439 test:
> > >
> > > https://launchpadlibrarian.net/97273119/buildlog_ubuntu-precise-i386.pspp_0.7.9%2Bgit20120318-0ubuntu1~bojo1~precise1_FAILEDTOBUILD.txt.gz
> > >  
> > >
> > > Am Mittwoch, den 14.03.2012, 22:15 -0700 schrieb Ben Pfaff:
> > >> Ben Pfaff <address@hidden> writes:
> > >> 
> > >> > John Darrington <address@hidden> writes:
> > >> >
> > >> >> 180 and 181 both relate to reading of openoffice.org
> > >> >> spreadsheet files and seem to be just warnings.  I wonder why
> > >> >> the problem didn't show up on debian?  Maybe a different libxml
> > >> >> library?  Since this xml is generated by openoffice itself,
> > >> >> there's probably not much we can do if libxml thinks it is
> > >> >> wrong.  Perhaps we should just change the test to ignore the
> > >> >> warning.
> > >> >
> > >> > Looking through my own builder's logs, I see at least three
> > >> > failures of these tests on different days (Feb. 29 and March 2
> > >> > and 3):
> > >> >
> > >> > http://pspp.benpfaff.org/~blp/pspp-master/20120229030501/testsuite.dir/
> > >> > http://pspp.benpfaff.org/~blp/pspp-master/20120302030501/testsuite.dir/
> > >> > http://pspp.benpfaff.org/~blp/pspp-master/20120303030503/testsuite.dir/
> > >> >
> > >> > Must be something nondeterministic at work.
> > >> 
> > >> I found it with valgrind and fixed it with this commit:
> > 
> 
>