[Hibernate] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors

2006-06-10 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20060610044855 TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:86: The following error occurred while executing this line:

[Hibernate] hibernate-mysql-testsuite Build Completed With Testsuite Errors

2006-06-10 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20060610045837 TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:121: The following error occurred while executing this line:

Re: [Hibernate] questions regarding development setup

2006-06-10 Thread Szczepan Faber
You're right. We should never have "expected failure" type tests in a test suite so that we can get back to things we know we want to fix. That is so crazy; what are we thinking here…ha ha ha :) Of course you should test non-happy path / expected failure / exception condition. But c reating

Re: [Hibernate] questions regarding development setup

2006-06-10 Thread Scott M Stark
Its more a limitation of the testing environment than project structure. One should be able to annotate known tests as failing at either the test or ci layer to achieve a simple boolean overall result as to whether the testsuite is in an expected state. -Original Message- From: [EMAIL

Re: [Hibernate] questions regarding development setup

2006-06-10 Thread Max Andersen
Title: RE: [Hibernate] questions regarding development setup Yes, but no such thing exist AFAIK. That is why we introduced this failureExpected notion. /max -Original Message- From: Scott M Stark Sent: Sat 10-06-2006 17:32 To: Max Andersen; Szczepan Faber Cc:

Re: [Hibernate] questions regarding development setup

2006-06-10 Thread Max Rydahl Andersen
You're right. We should never have expected failure type tests in a test suite so that we can get back to things we know we want to fix. That is so crazy; what are we thinking here… How can developer know if the codebase in svn is not broken? - only by comparing list of failures

[Hibernate] hibernate-timesten-testsuite Build Completed With Testsuite Errors

2006-06-10 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-timesten-testsuite?log=log20060610220011 TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:93: The following error occurred while executing this line:

[Hibernate] hibernate-oracle10-testsuite Build Completed With Testsuite Errors

2006-06-10 Thread qa
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20060611012422 TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:100: The following error occurred while executing this line: