jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

Where is this source coming from? The
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase(tests-security-basic-unit)
result shows 2 tests, but the Branch_4_2 codebase has 4, and
has is
using an invalid web context path.


jboss-qa-internalredhat.com wrote:
>  View results here ->
> http://cruisecon
trol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.5?l
og=log20070531052329
> 
> TESTS FAILED
> Ant Error
> Message:
/qa/services/cruisecontrol/work/scripts/build-jboss-common.x
ml:272:
> The following error occurred while executing this
line:
>
/qa/services/cruisecontrol/work/scripts/build-common-targets
.xml:26:
> Build Successful - Tests completed with errors or
failures.
> Date of build: 05/31/2007 05:23:29
> Time to build: 183 minutes 28 seconds
> Last changed: 05/30/2007 11:07:39
> Last log entry: JBPAPP-199, try jbossts 4.2.3.SP4
> 
>  Unit Tests: (4137)  Total Errors and Failures: (3)
>
testRecursiveLoadMT	org.jboss.test.classloader.test.Circular
ityUnitTestCase
> testSimpleEjb
>
org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTest
Case
>
testUnackedDurableTopic	org.jboss.test.jbossmq.test.UnackedU
nitTestCase
> 
>  
> 
>  Modifications since last build:  (first 50 of 155)
> 63257	modified	dimitrisjboss.org
>
//branches/Branch_4_2/build/build-thirdparty.xml	JBPAPP-199,
try jbossts
> 4.2.3.SP4
> 63249	modified	dimitrisjboss.org
> //branches/Branch_4_2/system/src/bin/run.bat	JBAS-4418,
run.bat should
> include %PATH% in java.library.path when bin/native
exists
> 63243	modified	dimitrisjboss.org
>
//branches/Branch_4_2/testsuite/src/main/org/jboss/test/iiop
/test/ParameterPassingStressTestCase.java
> JBAS-3613, test still doesn't pass on Sun/HP 1.5 JVMs,
after jacorb
> 2.3.0 upgrade.
>
63239	modified	wolfc	//branches/Branch_4_2/ejb3/build-from-5
.xml	WIP:
> compile from AS 5 source using AS 4.2
>
63238	added	wolfc	//branches/Branch_4_2/ejb3/build-from-5.xm
l	WIP: copy
> from build.xml
>
63237	deleted	wolfc	//branches/Branch_4_2/ejb3/build-from-5.
xml	
>
63236	added	wolfc	//branches/Branch_4_2/ejb3/build-from-5.xm
l	WIP:
> compile AS 5 code using AS 4.2
> 63229	modified	dimitrisjboss.org
>
//branches/Branch_4_2/testsuite/src/main/org/jboss/test/comp
atibility/test/SerialVersionUIDUnitTestCase.java
> JBAS-4146, generatied ties have different
serialVersionUIDs
> 63228	modified	dimitrisjboss.org
>
//branches/Branch_4_2/testsuite/src/main/org/jboss/test/comp
atibility/test/SerialVersionUIDUnitTestCase.java
> JBAS-4146, updated jacorb has different
serialVersionUIDs
>
63222	modified	wolfc	//branches/Branch_4_2/ejb3/build-test.x
ml	Merged
> build-simple macro from trunk
>
63222	added	wolfc	//branches/Branch_4_2/ejb3/imports/build-s
imple.xml
> Merged build-simple macro from trunk
> 63221	added	wolfc	//branches/Branch_4_2/ejb3/imports	
> 63217	modified	reverbel
>
//branches/Branch_4_2/iiop/src/main/org/jboss/iiop/jacorb/SS
LServerSocketFactory.java
> Modifications needed by JacORB 2.3.0jboss.patch1
(JBAS-4146). The
> changes in SSLSocketFactory/SSLServerSocketFactory and
> DomainSocketFactory reflect changes in JacORB's socket
factory APIs in
> JacORB 2.3.0.The change in
IIOPClientUserTransactionObjectFactory is due
> to the stricter type-checking done by the method narrow
in JacORB 2.3.0.
> 63217	modified	reverbel
>
//branches/Branch_4_2/iiop/src/main/org/jboss/tm/iiop/client
/IIOPClientUserTransactionObjectFactory.java
> Modifications needed by JacORB 2.3.0jboss.patch1
(JBAS-4146). The
> changes in SSLSocketFactory/SSLServerSocketFactory and
> DomainSocketFactory reflect changes in JacORB's socket
factory APIs in
> JacORB 2.3.0.The change in
IIOPClientUserTransactionObjectFactory is due
> to the stricter type-checking done by the method narrow
in JacORB 2.3.0.
> 63217	modified	reverbel
>
//branches/Branch_4_2/iiop/src/main/org/jboss/iiop/jacorb/SS
LSocketFactory.java
> Modifications needed by JacORB 2.3.0jboss.patch1
(JBAS-4146). The
> changes in SSLSocketFactory/SSLServerSocketFactory and
> DomainSocketFactory reflect changes in JacORB's socket
factory APIs in
> JacORB 2.3.0.The change in
IIOPClientUserTransactionObjectFactory is due
> to the stricter type-checking done by the method narrow
in JacORB 2.3.0.
> 63217	modified	reverbel
>
//branches/Branch_4_2/build/build-thirdparty.xml	Modificatio
ns needed by
> JacORB 2.3.0jboss.patch1 (JBAS-4146). The changes in
> SSLSocketFactory/SSLServerSocketFactory and
DomainSocketFactory reflect
> changes in JacORB's socket factory APIs in JacORB
2.3.0.The change in
> IIOPClientUserTransactionObjectFactory is due to the
stricter
> type-checking done by the method narrow in JacORB
2.3.0.
> 63217	modified	reverbel
>
//branches/Branch_4_2/security/src/main/org/jboss/security/s
sl/DomainSocketFactory.java
> Modifications needed by JacORB 2.3.0jboss.patch1
(JBAS-4146). The
> changes in SSLSocketFactory/SSLServerSocketFactory and
> DomainSocketFactory reflect changes in JacORB's socket
factory APIs in
> JacORB 2.3.0.The change in
IIOPClientUserTransactionObjectFactory is due
> to the stricter type-checking done by the method narrow
in JacORB 2.3.0.
> 63211	modified	weston.pricejboss.com
>
//branches/Branch_4_2/connector/src/main/org/jboss/resource/
adapter/jms/JmsSession.java
> [JBCTS-588] As per the JMS specification, an
IllegalStateException
> should be thrown when certain methods are used against
the wrong
> messaging domaintype. JMS 1.1 specification Sections
11.2.
> 63208	modified	scott.starkjboss.org
>
//branches/Branch_4_2/jmx/src/main/org/jboss/mx/loading/Clas
sLoadingTask.java
> JBPAPP-64, JBAS-4066 enforce a maximum bound on
> LinkageError/ClassCircularity errors
> 63208	modified	scott.starkjboss.org
>
//branches/Branch_4_2/jmx/src/main/org/jboss/mx/loading/Load
Mgr3.java
> JBPAPP-64, JBAS-4066 enforce a maximum bound on
> LinkageError/ClassCircularity errors
> 63205	modified	dimitrisjboss.org
> //branches/Branch_4_2/testsuite/build.xml	JBAS-4416,
Introduce
> compatibility tests for interoperating with older jboss
versions using
> the legacy rmi invokers
> 63204	added	dimitrisjboss.org
>
//branches/Branch_4_2/testsuite/src/resources/test-configs/l
egacy-invokers
> JBAS-4416, Introduce compatibility tests for
interoperating with older
> jboss versions using the legacy rmi invokers
> 63204	added	dimitrisjboss.org
>
//branches/Branch_4_2/testsuite/src/resources/test-configs/l
egacy-invokers/conf
> JBAS-4416, Introduce compatibility tests for
interoperating with older
> jboss versions using the legacy rmi invokers
> 63204	added	dimitrisjboss.org
>
//branches/Branch_4_2/testsuite/src/resources/test-configs/l
egacy-invokers/conf/standardjboss.xml
> JBAS-4416, Introduce compatibility tests for
interoperating with older
> jboss versions using the legacy rmi invokers
> 63202	modified	dimitrisjboss.org
>
//branches/Branch_4_2/server/src/main/org/jboss/metadata/Con
figurationMetaData.java
> JBAS-4444, use the base configuration
invoker-proxy-binding-name if it's
> not specified in the sub-configuration.
> 63201	modified	dbhole
>
//branches/Branch_4_2/varia/src/main/org/jboss/jdbc/Hyperson
icDatabase.java
> JBPAPP-193: Fixed HypersonicDatabase.java to detect
HeadlessException
> wrapped inside an InvocationTargetException
> 63190	modified	thomas.dieslerjboss.com
>
//branches/Branch_4_2/server/src/main/org/jboss/metadata/Ejb
PortComponentMetaData.java
> Remove <port-component-uri> first token as
<context-root>
> 63183	modified	wolfc	//branches/Branch_4_2/ejb3	Added
tag
> JBoss_4_2_0_CR1 and JBoss_4_2_0_GA
> 63178	modified	alex.loubyanskyjboss.com
>
//branches/Branch_4_2/testsuite/src/main/org/jboss/test/cmp2
/optimisticlock/interfaces/Facade.java
> JBPAPP-173 sleep before the concurrent transaction
commits, not after
> 63178	modified	alex.loubyanskyjboss.com
>
//branches/Branch_4_2/testsuite/src/main/org/jboss/test/cmp2
/optimisticlock/ejb/FacadeBean.java
> JBPAPP-173 sleep before the concurrent transaction
commits, not after
> 63177	modified	scott.starkjboss.org
> //branches/Branch_4_2/tomcat/build.xml	JBCTS-591, add
dependnecy on the
> iiop module
> 63177	modified	scott.starkjboss.org
> //branches/Branch_4_2/tomcat/.classpath	JBCTS-591, add
dependnecy on the
> iiop module
> 63176	modified	scott.starkjboss.org
>
//branches/Branch_4_2/tomcat/src/main/org/jboss/web/tomcat/s
ervice/WebAppClassLoader.java
> JBCTS-591, Generate iiop stubs dynamically for any name
ending in _Stub.
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/fireb
ird-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/sapdb
-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/point
base-xa-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/infor
mix-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/mssql
-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/infor
mix-xa-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/progr
ess-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/mssql
-xa-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/mysql
-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/oracl
e-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/postg
res-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/db2-d
s.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/db2-4
00-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/mimer
-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/db2-j
cc-xa-ds.xml	Removed
> optional comment for metadata/type-mapping as it is not
unless the
> defaults/datasource-mapping is commented out or defined
in jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/solid
-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 63175	modified	rrajesh
>
//branches/Branch_4_2/connector/src/etc/example-config/oracl
e-xa-ds.xml
> Removed optional comment for metadata/type-mapping as
it is not unless
> the defaults/datasource-mapping is commented out or
defined in
> jbosscmp-jdbc.xml
> 
> 
>
------------------------------------------------------------
------------
> 
> _______________________________________________
> jboss-development mailing list
> jboss-developmentlists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

When I run the tests-security-basic-unit the
CustomPrincipalPropagationUnitTestCase fails as I expect:

[starksmsuccubus testsuite]$ ant tests-security-basic-unit
...
    [junit] Tests run: 4, Failures: 1, Errors: 2, Time
elapsed: 1.047 sec
    [junit] Test
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase FAILED

I don't know what is going into the reports.

Scott M Stark wrote:
> Where is this source coming from? The
>
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase(tests-security-basic-unit)
> result shows 2 tests, but the Branch_4_2 codebase has
4, and has is
> using an invalid web context path.
> 
> 
> jboss-qa-internalredhat.com wrote:
>>  View results here ->
>> http://cruisecon
trol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.5?l
og=log20070531052329
>>
>> TESTS FAILED
>> Ant Error
>> Message:
/qa/services/cruisecontrol/work/scripts/build-jboss-common.x
ml:272:
>> The following error occurred while executing this
line:
>>
/qa/services/cruisecontrol/work/scripts/build-common-targets
.xml:26:
>> Build Successful - Tests completed with errors or
failures.
>> Date of build: 05/31/2007 05:23:29
>> Time to build: 183 minutes 28 seconds
>> Last changed: 05/30/2007 11:07:39
>> Last log entry: JBPAPP-199, try jbossts 4.2.3.SP4
>>
>>  Unit Tests: (4137)  Total Errors and Failures:
(3)
>>
testRecursiveLoadMT	org.jboss.test.classloader.test.Circular
ityUnitTestCase
>> testSimpleEjb
>>
org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTest
Case
>>
testUnackedDurableTopic	org.jboss.test.jbossmq.test.UnackedU
nitTestCase
>>
>>  
>>
>
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Could it be related to:
http://ji
ra.jboss.com/jira/browse/JBAS-4103

Scott M Stark wrote:
> When I run the tests-security-basic-unit the
> CustomPrincipalPropagationUnitTestCase fails as I
expect:
> 
> [starksmsuccubus testsuite]$ ant
tests-security-basic-unit
> ...
>     [junit] Tests run: 4, Failures: 1, Errors: 2, Time
elapsed: 1.047 sec
>     [junit] Test
>
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase FAILED
> 
> I don't know what is going into the reports.
> 
> Scott M Stark wrote:
>> Where is this source coming from? The
>>
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase(tests-security-basic-unit)
>> result shows 2 tests, but the Branch_4_2 codebase
has 4, and has is
>> using an invalid web context path.
>>
>>
>> jboss-qa-internalredhat.com wrote:
>>>  View results here ->
>>> http://cruisecon
trol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.5?l
og=log20070531052329
>>>
>>> TESTS FAILED
>>> Ant Error
>>> Message:
/qa/services/cruisecontrol/work/scripts/build-jboss-common.x
ml:272:
>>> The following error occurred while executing
this line:
>>>
/qa/services/cruisecontrol/work/scripts/build-common-targets
.xml:26:
>>> Build Successful - Tests completed with errors
or failures.
>>> Date of build: 05/31/2007 05:23:29
>>> Time to build: 183 minutes 28 seconds
>>> Last changed: 05/30/2007 11:07:39
>>> Last log entry: JBPAPP-199, try jbossts
4.2.3.SP4
>>>
>>>  Unit Tests: (4137)  Total Errors and Failures:
(3)
>>>
testRecursiveLoadMT	org.jboss.test.classloader.test.Circular
ityUnitTestCase
>>> testSimpleEjb
>>>
org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTest
Case
>>>
testUnackedDurableTopic	org.jboss.test.jbossmq.test.UnackedU
nitTestCase
>>>
>>>  
>>>
> 
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

No, I just had too many workspaces open and ended up copying
the test
from trunk. When I reverted everything its back to what the
test report
says:

    [junit] Running
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time
elapsed: 1.03 sec


Dimitris Andreadis wrote:
> Could it be related to:
> http://ji
ra.jboss.com/jira/browse/JBAS-4103
> 
> Scott M Stark wrote:
>> When I run the tests-security-basic-unit the
>> CustomPrincipalPropagationUnitTestCase fails as I
expect:
>>
>> [starksmsuccubus testsuite]$ ant
tests-security-basic-unit
>> ...
>>     [junit] Tests run: 4, Failures: 1, Errors: 2,
Time elapsed: 1.047 sec
>>     [junit] Test
>>
org.jboss.test.security.test.CustomPrincipalPropagationUnitT
estCase
>> FAILED
>>
>> I don't know what is going into the reports.

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment