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

Disable SASL Tests for Java versions >22 #29455

Conversation

abutch3r
Copy link
Member

@abutch3r abutch3r commented Aug 21, 2024

The Kafka Client's SASL code uses the Java security, which as of Java 23 now throws exceptions if used. there is currently no Kafka Client version that does not use Security Manager. To allow for the rest of the RM suite of tests to continue passing without the failing Java 23 build, set the maximum java level to 21.

This limitation should be removed once a suitable client is available and included.

The Kafka Client's SASL code uses the Java security, which as of Java 23 now throws exceptions if used. there is currently no Kafka Client version that does not use Security Manager. To allow for the rest of the RM suite of tests to continue passing without the failing Java 23 build, set the maximum java level to 21.

This limitation should be removed once a suitable client is available and included.
@abutch3r
Copy link
Member Author

#build

@LibbyBot
Copy link

Your personal pipeline request is at https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?uuid=a3aae66e-7ffd-4939-8625-c858861feaa6

Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_xwlqIF-aEe-4wdAm7liz3w

The build will run your changed FAT bucket(s) 10 times.

Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

@LibbyBot
Copy link

The build abutch3r-29455-20240821-0302
https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_xwlqIF-aEe-4wdAm7liz3w
completed successfully!

@abutch3r
Copy link
Member Author

abutch3r commented Aug 22, 2024

Java 23 pipeline build - https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?pipelineId=e9433c04-ba63-4649-8eb8-8c9af1ce3a08

Previously
image
Now
image

The 20 previously failing tests are now being correctly excluded from Java23 runs.

While there are 6 excluded tests - the checkpoint test would not run as part of the current Java23 builds given that is currently running a non-semeru JVM

@gjwatts
Copy link
Member

gjwatts commented Aug 22, 2024

#build

@gjwatts gjwatts changed the title Disable SASL Tests for Java versions >21 Disable SASL Tests for Java versions >22 Aug 22, 2024
@LibbyBot
Copy link

Your personal pipeline request is at https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?uuid=79ba39a4-d5f1-43cb-83ae-dca6f2c03ced

Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_2wE44GDMEe-4wdAm7liz3w

The build will run your changed FAT bucket(s) 10 times.

Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

@LibbyBot
Copy link

The build abutch3r-29455-20240822-2229
https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_2wE44GDMEe-4wdAm7liz3w
completed successfully!

@gjwatts
Copy link
Member

gjwatts commented Aug 24, 2024

#libbybot

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • Please describe in a separate comment how you tested your changes.

  • 6 FAT files were changed, added, or removed.

  • Check that the build did not break the affected FAT suite(s).

@gjwatts
Copy link
Member

gjwatts commented Aug 24, 2024

Normal PB was clean, Java 23 PB was clean. Merging.

@gjwatts gjwatts merged commit d1a2c21 into OpenLiberty:integration Aug 24, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants