Re: [jakartaee-tck-dev] Platform TCK run started

[Scott Marlow <smarlow@xxxxxxxxxx>]

On Wed, Jun 10, 2020 at 2:54 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

On Wed, Jun 10, 2020 at 10:47 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

We just started the nightly Platform TCK run with today's GlassFish master changes (which includes the ORB switch to use jakarta package classes).

https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-nightly-run-master/41/ is the link for the test run.

We stopped the run after 20 hours, if you open https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/682 and right button click on "View as plain text" on left side of window, then "save the link as..." to save the consoleText file locally.

As you probably have guessed, the consoleText will show the test output for all jobs that have run and can only be accessed by those that can login the Eclipse CI TCK Jenkins server.  If you don't have access but would like to see the output, let me know and I will find a way to upload a zip of the text file somewhere.  

The above mentioned consoleText download, shows "NoClassDefFoundError: com/sun/ts/tests/common/connector/util/TSMessageListenerInterface" which should of been resolved via whitebox.jar.  The whitebox.jar should of been resolved via the whitebox-anno_no_md.rar which has whitebox.jar referenced from MANIFEST.MF:

"

Extension-List: tsharness cts whitebox
tsharness-Extension-Name: tsharness
tsharness-Specification-Version: 1.4
tsharness-Implementation-Version: 1.4
tsharness-Implementation-Vendor-Id: com.sun
cts-Extension-Name: cts
cts-Specification-Version: 1.4
cts-Implementation-Version: 1.4
cts-Implementation-Vendor-Id: com.sun
whitebox-Extension-Name: whitebox
whitebox-Specification-Version: 1.6
whitebox-Implementation-Version: 1.6
whitebox-Implementation-Vendor-Id: com.sun
"

 

In the GlassFish 6.0 server.log (engineering build from yesterday that includes the ORB patch), we see "NoClassDefFoundError: com/sun/ts/tests/common/connector/util/TSMessageListenerInterface" (see https://gist.github.com/scottmarlow/cd9b9477997abb1f4664125c9e25076b for full exception call stack).  The server.log is contained in https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/682/artifact/connector-results.tar.gz

https://gist.github.com/scottmarlow/1bb37ec92bf6daa1b98ebbbe1e752d13 shows a "IllegalArgumentException: [com.sun.ts.tests.common.connector.whitebox.TSConnectionFactory] is not an allowed property value type" 

Would it help to add --verbose option when starting GlassFish to get more information from GlassFish?  Anything else that we should do?

One other thing that we are doing for whitebox.jar, is switching from the older javax based schema definitions to Jakarta EE 9 schema definitions that reference jakarta.resource.spi.security.PasswordCredential, this should help with failures like:

"Value 'jakarta.resource.spi.security.PasswordCredential' is not facet-valid with respect to enu
meration '[javax.resource.spi.security.PasswordCredential, org.ietf.jgss.GSSCredential, javax.resource.spi.security.GenericCredential]'. It must be a value from the enumeration.

"
Perhaps this will be a root cause issue for many failures.  This should address https://github.com/eclipse-ee4j/jakartaee-tck/issues/266.

Scott 

Scott