Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

glassfish 7 EL TCK failures JDK 11 and JDK 17 #23900

Closed
gurunrao opened this issue Apr 12, 2022 · 4 comments
Closed

glassfish 7 EL TCK failures JDK 11 and JDK 17 #23900

gurunrao opened this issue Apr 12, 2022 · 4 comments
Assignees
Labels
ee10-tck EE 10 TCK failures

Comments

@gurunrao
Copy link
Contributor

gurunrao commented Apr 12, 2022

Following EL TCK failures are seen with Glassfish 7 JDK 11 and JDK 17 runs:

Found a new failure:TestCase{testName=methodExpressionMatchingAmbiguousTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodexpression.ELClient, status=FAILED}
Found a new failure:TestCase{testName=methodExpressionMatchingCoercionBeatsExactVarArgsTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodexpression.ELClient, status=FAILED}
Found a new failure:TestCase{testName=methodExpressionMatchingExactPreferredTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodexpression.ELClient, status=FAILED}
Found a new failure:TestCase{testName=methodExpressionMatchingOverloadBeatsCoercionTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodexpression.ELClient, status=FAILED}
Found a new failure:TestCase{testName=methodExpressionMatchingOverloadBeatsExactVarArgsTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodexpression.ELClient, status=FAILED}
Found a new failure:TestCase{testName=methodExpressionMatchingVarArgsTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodexpression.ELClient, status=FAILED}
Found a new failure:TestCase{testName=methodReferenceTest_from_standalone, className=com.sun.ts.tests.el.api.jakarta_el.methodreference.ELClient, status=FAILED}
Found a new failure:TestCase{testName=elCoerceLambdaExpressionToFunctionalInterfaceTest_from_standalone, className=com.sun.ts.tests.el.spec.coercion.ELClient, status=FAILED}
Found a new failure:TestCase{testName=elCoerceToArrayTest_from_standalone, className=com.sun.ts.tests.el.spec.coercion.ELClient, status=FAILED}

More details can be analyzed using eltck.log
CI run details : https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1740/testReport/
Test result archive(with glassfish server log): expression-language-tck-results.tar.gz

CC @markt-asf

@gurunrao gurunrao added the ee10-tck EE 10 TCK failures label Apr 12, 2022
@arjantijms
Copy link
Contributor

I'm going to take a look at them, thanks @gurunrao for the notice!

@arjantijms arjantijms self-assigned this Apr 12, 2022
@arjantijms
Copy link
Contributor

Locally only 1 failure left. I hope to fix that one today.

@arjantijms
Copy link
Contributor

TCK now fully passed locally:

[INFO]      [exec] [javatest.batch] ********************************************************************************
[INFO]      [exec] [javatest.batch] Number of tests completed:  350 (350 passed, 0 failed, 0 with errors)
[INFO]      [exec] [javatest.batch] Number of tests remaining:  0
[INFO]      [exec] [javatest.batch] ********************************************************************************
[INFO]      [exec] [javatest.batch] Completed running 350 tests.
[INFO]      [exec] [javatest.batch] Number of Tests Passed      = 350
[INFO]      [exec] [javatest.batch] Number of Tests Failed      = 0
[INFO]      [exec] [javatest.batch] Number of Tests with Errors = 0
[INFO]      [exec] [javatest.batch] ********************************************************************************

@arjantijms
Copy link
Contributor

See eclipse-ee4j/expressly#8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ee10-tck EE 10 TCK failures
Projects
None yet
Development

No branches or pull requests

2 participants