Test on Java 17 #583
Merged
Test on Java 17 #583
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In general, it is not possible in glibc (i.e., most Linux systems) to change environment variables after a program has launched, at least for multi-threaded programs. In earlier versions of Java it was possible to fake this at the Java runtime level by using reflection to access the Java hash map that mirrored the process's environment variables in the operating system, but recent versions of Java close off these reflection-based tricks. As such I am simply removing any tests that try to do this. I left the most important test with
@Ignorein case someone needs to run it manually specifying the needed environment variable.