They were most probably not failing before 1.8 was released, see: http://dash.orfeo-toolbox.org/index.php?project=QGIS&date=2012-06-13
On Fri, Jun 15, 2012 at 12:53 PM, Marco Hugentobler <[email protected]> wrote: >> OTOH, the results for final-1_8_0 of qgis_rasterlayertest are much >> better than latest master. > > > That's because of the raster_resampler merge. Something to look at for me. > No idea why they fail before (probably it depends on the GDAL you are > using). The autobuilds use a variety of gdal version (1-6 -> 1.9.1) so I think most possibilities are covered - so it's probably a local problem. > > For me, there is also > > 11/20 Test #11: qgis_geometrytest ....................***Failed 0.44 sec > > and the application hangs with qgis_ziplayertest : > > Start 17: qgis_ziplayertest > *** glibc detected *** > /home/marco/src/Quantum-GIS/build/output/bin/qgis_ziplayertest: corrupted > double-linked list: 0x000000000266fc20 *** This is after raster_resampler merge right? Which gdal version and OS are you using? Please send me a debug log of that test. > > Regards, > Marco > > Am 15.06.2012 17:44, schrieb Radim Blazek: > >> I wanted to bisect the first wrong commit after 1.8 but I found that >> final-1_8_0 also fails in qgis_rasterlayertest and qgis_rendererstest. >> Is it possible? Release was made with broken tests? Is it my local >> problem? Are the tests independent of user settings? >> >> OTOH, the results for final-1_8_0 of qgis_rasterlayertest are much >> better than latest master. >> >> Radim >> >> >> On Fri, Jun 15, 2012 at 11:41 AM, Tim Sutton<[email protected]> wrote: >>> >>> Hi All >>> >>> I just want to make a heartfelt plea that any new code pushed to Git >>> master should not break tests (at minimum on the platform on which you >>> are working). If you do radical changes, the test suite should be >>> updated to accommodate them so that the tests still pass for your >>> platform when you commit. I would like to see the test suite grow to >>> encompass as much functionality of QGIS as possible, but it will be >>> very difficult to maintain them if we commit code that breaks them. >>> You can always view the state of the last nightly builds here: >>> >>> http://dash.orfeo-toolbox.org/index.php?project=QGIS >>> >>> You can test your work before pusing it to master by doing: >>> >>> make test >>> make check >>> >>> or (to share your test results) >>> >>> make Experimental >>> >>> Thanks! >>> >>> Regards >>> >>> >>> >>> -- >>> Tim Sutton - QGIS Project Steering Committee Member (Release Manager) >>> ============================================== >>> Please do not email me off-list with technical >>> support questions. Using the lists will gain >>> more exposure for your issues and the knowledge >>> surrounding your issue will be shared with all. >>> >>> Visit http://linfiniti.com to find out about: >>> * QGIS programming and support services >>> * Mapserver and PostGIS based hosting plans >>> * FOSS Consulting Services >>> Skype: timlinux >>> Irc: timlinux on #qgis at freenode.net >>> ============================================== >>> _______________________________________________ >>> Qgis-developer mailing list >>> [email protected] >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > -- > Dr. Marco Hugentobler > Sourcepole - Linux& Open Source Solutions > Weberstrasse 5, CH-8004 Zürich, Switzerland > [email protected] http://www.sourcepole.ch > Technical Advisor QGIS Project Steering Committee > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
