|Re: [jakartaee-platform-dev] [jakartaee-tck-dev] Stable location of GF 6 used to pass TCK?|
There are signature test failures for connector, jaspic & jsp
for which I need to verify the signature files with the jars in
glassfish. But these are the major failures for standalone TCKs.
Few of the below should be resolved by now. I will send out a
recent test run result for all standalone TCKs in few hours to
I have not covered mail & activation TCKs in this list.
Are these the only standalone TCKs with failures?
The standalone TCKs with consistent failures are present at .
authentication-tck : 1 signature test (need to verify the signatures with the current jars in glassfish)
restful-ws-tck : 2 failures (https://github.com/eclipse-ee4j/glassfish/issues/23122 )
security-tck : 5 test failures (https://github.com/eclipse-ee4j/glassfish/issues/23130 will probably address most)
websocket-tck :1 signature test ( https://github.com/eclipse-ee4j/glassfish/issues/23128 )
The platform TCK will have more failures and we do not have a recent test run for those.
Thanks & Regards,
On 21/07/20 5:33 pm, Alwin Joseph wrote:
I will send a detailed report of test run status.
For the initial waves(wave 0 & wave 1), we have 1 signature test failure in Websocket TCK when run with glassfish (issue : https://github.com/eclipse-ee4j/glassfish/issues/23128)
On 21/07/20 2:18 pm, Steve Millidge (Payara) wrote:
I’d like to get to an understanding of where we are on TCK testing. What suites pass, which have a small number of failures and which have a large number? That way I can seek volunteers to focus on each test suite.
If a number of specs, currently pass their TCK, and need a milestone release to reference in their spec compliance PRs, we can create one and that way we can have a download for them to point to. However I don’t want to do this spec by spec.
I will raise at the platform dev meeting today.
On Mon, Jul 20, 2020 at 2:58 PM Alwin Joseph <alwin.joseph@xxxxxxxxxx> wrote:
I think it would help if the full & web profile bundles are updated at https://download.eclipse.org/ee4j/glassfish/ to run the tests for the certification.
I can update something there too, but I'll wait for some of the other GlassFish committers to agree with that.
It should also be ok to upload it in a Github release if that is more stable. In this case the bundle will be considered final I believe.
Okay, I just did that:
The build that passes the Servlet TCK at least (and possibly more), is this one: https://github.com/eclipse-ee4j/glassfish/releases/download/M2-servlet5/glassfish.zip
In order to pass TCKs in GlassFish 6, for instance the Servlet 5 TCK, I can reference the Jenkins archived build.
We were referring to the last successful build to get latest glassfish build from the source using  in tck CI to run tests with latest changes.
Yes, that's the same URL I've been using.
_______________________________________________jakartaee-platform-dev mailing listTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________ jakartaee-tck-dev mailing list jakartaee-tck-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
Back to the top