Sjoerd et al., after a clean rebuild from scratch, also my testing works fine again: testing status with changeset 42833:5b1a1f5ea1e8: monetdb5: !ERROR: Testing FAILED SIGNIFICANTLY (4 out of 494 tests failed) 1 out of 494 tests ran into timeout 4 out of 494 tests produced SIGNIFICANTLY different output sql: !ERROR: Testing FAILED SIGNIFICANTLY (4 out of 1161 tests failed) 15 out of 1161 tests could not be executed 1 out of 1161 tests produced slightly different output 3 out of 1161 tests produced SIGNIFICANTLY different output geom: !ERROR: Testing FAILED SIGNIFICANTLY (1 out of 16 tests failed) 1 out of 16 tests resulted in a crash I had originally done a delta-build from changeset 42814:e5fc6643697a to 42826:10d948cdb1be and noticed the testing problems. This triggered me to do a clean rebuild from scratch. However, instead of doing this with changeset 42826:10d948cdb1be and testing only that, I did the clean rebuild from scratch with changeset 42817:66a217e59090 (the first after 42814:e5fc6643697a that I had tested last), and then delta builds and testing for all changeset on the default branch between 42814:e5fc6643697a & 42826:10d948cdb1be. Thus, I did not build changeset 42825:f15583fdc322 clean from scratch but rather as delta over its predecessor 42821:3967ec4a8aef, and that seems to have caused the problems I experienced. My apologies for the "premature noise" I made. Stefan On Sat, Jan 14, 2012 at 10:20:02AM +0100, Stefan Manegold wrote:
Sjoerd et al.,
nightly testing does not seem to confirm the problem I encounter:
http://monetdb.cwi.nl/testweb/web/status.php http://monetdb.cwi.nl/testweb/web/testgrid.php?serial=42830:c3830ea8b04f&order=platform,arch,compiler
I'm investigating what is different in my case.
Stefan
On Fri, Jan 13, 2012 at 11:37:58PM +0100, Stefan Manegold wrote:
(on my 64-bit Fedora 14 desktop) this checkin seems cause several tests to fail or even crash:
testing status with changeset 42821:3967ec4a8aef:
monetdb5: !ERROR: Testing FAILED SIGNIFICANTLY (4 out of 494 tests failed) 1 out of 494 tests ran into timeout 3 out of 494 tests produced SIGNIFICANTLY different output
sql: !ERROR: Testing FAILED SIGNIFICANTLY (4 out of 1161 tests failed) 15 out of 1161 tests could not be executed 1 out of 1161 tests produced slightly different output 3 out of 1161 tests produced SIGNIFICANTLY different output
geom: !ERROR: Testing FAILED SIGNIFICANTLY (1 out of 16 tests failed) 1 out of 16 tests resulted in a crash
testing status with changeset 42825:f15583fdc322
monetdb5: !ERROR: Testing FAILED SIGNIFICANTLY (21 out of 494 tests failed) 1 out of 494 tests ran into timeout 20 out of 494 tests produced SIGNIFICANTLY different output
sql: !ERROR: Testing FAILED SIGNIFICANTLY (909 out of 1161 tests failed) 248 out of 1161 tests could not be executed 6 out of 1161 tests ran into timeout 900 out of 1161 tests resulted in a crash 3 out of 1161 tests produced SIGNIFICANTLY different output
geom: !ERROR: Testing FAILED SIGNIFICANTLY (16 out of 16 tests failed) 16 out of 16 tests resulted in a crash
I have not yet looked into the details.
Stefan
-- | Stefan.Manegold @ CWI.nl | DB Architectures (INS1) | | http://CWI.nl/~manegold/ | Science Park 123 (L321) | | Tel.: +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |