| Re: [openmq-dev] Release tracking for OpenMQ |
Here's the first failure from the log (confirms the version number is not matching):
[javatest.batch] ********************************************************************************
[javatest.batch] Beginning Test: com/sun/ts/tests/jms/core/queueConnection/QueueConnectionTests.java#metaDataTests_from_standalone
[javatest.batch] ********************************************************************************
[javatest.batch]
[javatest.batch] 10-20-2020 21:55:35: Harness - harness.executeMode is set to "2"
[javatest.batch] 10-20-2020 21:55:35: Harness - keywords (to be passed to tests) set to: all
[javatest.batch] 10-20-2020 21:55:35: Harness - sClassPathFromExecProps =
[javatest.batch] command: com.sun.ts.lib.harness.ExecTSTestCmd CLASSPATH=:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../lib/tsharness.jar:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../lib/sigtest.jar:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../lib/jmstck.jar:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../classes:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../bin:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/glassfish6/mq/lib/imq.jar:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/glassfish6/mq/lib/jms.jar:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/glassfish6/mq/lib/fscontext.jar:/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../bin/xml/impl/ri DISPLAY=:0.0 HOME=/home/jenkins windir= SYSTEMROOT= /opt/tools/java/oracle/jdk-8/1.8.0_202/jre/bin/java -Djava.security.policy=/home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../bin/harness.policy -Djava.security.manager -Ddeliverable.class=com.sun.ts.lib.deliverable.jms.JMSDeliverable -Djava.endorsed.dirs= com.sun.ts.tests.common.vehicle.VehicleClient -p /home/jenkins/agent/workspace/2_openmq-run-tck-against-staged-build/messaging-tck/bin/xml/../../tmp/tstest.jte -t metaDataTests -vehicle standalone
[javatest.batch] ************************************************************
[javatest.batch] * props file set to "/tmp/jenkins-cts-props.txt"
[javatest.batch] ************************************************************
[javatest.batch] 10-20-2020 21:55:35: TSJMSObjects.getJMSObjectsInstance()
[javatest.batch] 10-20-2020 21:55:35: Porting implementation class=com.sun.ts.lib.implementation.sun.jms.SunRIJMSObjects
[javatest.batch] 10-20-2020 21:55:35: ERROR: Error: incorrect JMSVersion=3.0
[javatest.batch] 10-20-2020 21:55:35: ERROR: Error: incorrect JMSMajorVersion=3
[javatest.batch] 10-20-2020 21:55:35: TSJMSObjects.getJMSObjectsInstance()
[javatest.batch] 10-20-2020 21:55:35: Porting implementation class=com.sun.ts.lib.implementation.sun.jms.SunRIJMSObjects
[javatest.batch] 10-20-2020 21:55:35: ERROR: Error: incorrect JMSVersion=3.0
[javatest.batch] 10-20-2020 21:55:35: ERROR: Error: incorrect JMSMajorVersion=3
[javatest.batch] 10-20-2020 21:55:36: ERROR: Error: metaDataTests failed
[javatest.batch] 10-20-2020 21:55:36: ERROR: Test case throws exception: Error: metaDataTests failed
[javatest.batch] 10-20-2020 21:55:36: ERROR: Exception at:
[javatest.batch] 10-20-2020 21:55:36: ERROR: com.sun.ts.lib.harness.EETest$Fault: Error: metaDataTests failed
[javatest.batch] at com.sun.ts.tests.jms.core.queueConnection.QueueConnectionTests.metaDataTests(QueueConnectionTests.java:281)
[javatest.batch] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[javatest.batch] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[javatest.batch] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[javatest.batch] at java.lang.reflect.Method.invoke(Method.java:498)
[javatest.batch] at com.sun.ts.lib.harness.EETest.run(EETest.java:596)
[javatest.batch] at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:115)
[javatest.batch] at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:40)
[javatest.batch] at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:105)
[javatest.batch] at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:486)
[javatest.batch] at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209)
[javatest.batch] at com.sun.ts.lib.harness.EETest.run(EETest.java:285)
[javatest.batch] at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:38)
[javatest.batch]
[javatest.batch] 10-20-2020 21:55:36: Cleanup: Closing Queue Connections
[javatest.batch] STATUS:Failed.Test case throws exception: Error: metaDataTests failed
[javatest.batch] Failed. Test case throws exception: Error: metaDataTests failed
[javatest.batch] ********************************************************************************
[javatest.batch] Finished Test: FAILED........com/sun/ts/tests/jms/core/queueConnection/QueueConnectionTests.java#metaDataTests_from_standalone
Hi,
Latest TCK script has been updated to take the JMSRA from the OpenMQ distro and update GF with it. See the run at: https://ci.eclipse.org/openmq/job/2_openmq-run-tck-against-staged-build/7/
Kind regards,Arjan Tijms
On Tue, Oct 20, 2020 at 11:20 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,
Indeed work in progress as you looked at it. As the mq/bin/* files are normally executable when built with GF, we have to take a look at what's exactly happening here.
The initial run has finished now and shows 4 failures:
[javatest.batch] Number of Tests Passed = 900[javatest.batch] Number of Tests Failed = 4[javatest.batch] Number of Tests with Errors = 0
They're all MetaDataTest related.
I'll take a look at whether the JMSRA needs to be updated.
Kind regards,Arjan Tijms
On Tue, Oct 20, 2020 at 10:28 PM Piotr Żygieło <piotr@xxxxxxxxxx> wrote:
I've updated https://github.com/eclipse-ee4j/openmq/issues/586 to add
info about executability of mq/bin/* files.
_______________________________________________
openmq-dev mailing list
openmq-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/openmq-dev
_______________________________________________ openmq-dev mailing list openmq-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/openmq-dev__;!!GqivPVa7Brio!PT97oh2GcKi8Qx-lO43AVvzfiYrNK1BjW0-m5U_bn6dZ4I5ZXsTXUVFcc_PwmyY$