View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20060611015557
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:121: The following error occurred while executing this line: /home/cruisecontrol/work/sc
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: /home/cruisecontrol/work
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20060610222334
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 06/10/2006 22:23:34Time to build:
Unit Tests: (0) Total Errors and Failures
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: /home/cruisecontrol/work/
JUnit 4.x has @Ignore annotation.On 6/10/06, Scott M Stark <[EMAIL PROTECTED]> wrote:
Then we need to fix it.http://jira.jboss.com/jira/browse/JBQA-383
> -Original Message-> From: Max Andersen> Sent: Saturday, June 10, 2006 10:21 AM> To: Scott M Stark; Szczepan Faber> Cc:
hibernate-devel@l
Then we need to fix it.
http://jira.jboss.com/jira/browse/JBQA-383
> -Original Message-
> From: Max Andersen
> Sent: Saturday, June 10, 2006 10:21 AM
> To: Scott M Stark; Szczepan Faber
> Cc: hibernate-devel@lists.sourceforge.net
> Subject: RE: [Hibernate] questions regarding development
>> 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 o
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: hibernate-devel@lists.
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
> 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
fa
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: /home/cruisecontrol/work/sc
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: /home/cruisecontrol/work/sc
12 matches
Mail list logo