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

external tests are unable to test "some" jdks #5477

Open
judovana opened this issue Aug 1, 2024 · 0 comments
Open

external tests are unable to test "some" jdks #5477

judovana opened this issue Aug 1, 2024 · 0 comments

Comments

@judovana
Copy link
Contributor

judovana commented Aug 1, 2024

The external tests are runnign by default in container, and are mounting jdk inside. If the jdk is not exactly standalone (quite common is symlink to system tzdata and cacerts) then the jdk can not be tested

In my case, the "some" means jdks with symlink to keystore, which when mounted is not resolved, and thus jdk fails to even print hello world.

Any thoughts on this?

The only one I have is to add option, that such jdk will not be mounted, but copied in, with all symlinks resolved during copy....

Another - better, but not that srigtforward solution may be to scan the future "/opt/java/openjdk/" in runtime, and try to copy-in missing resources.
Another one may be to overwrite the known symlinked locations by -DcacertLocation -Dkeystore .. This is nicely moving it to user space, But afaik there is none -D for tzdata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant