-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
Windows jdk_native_sanity test fails on azure machines #1471
Comments
I presume you are doing extra triage on this one, to verify that this is what it looks like, a difference in machine config, and subsequently would be raised in the openjdk-infrastructure repo. |
I assume it will end up being something which needs fixing in the machines, but it's not obvious to me what the difference is. Can't be as simple as unzip not being present (failing to unzip the test package) because the jdk under test is also unzipped. |
Yes I am just encouraging the raisers to further triage the issues they raise, following the triage guidance in order to avoid a pile of stale issues (as there are no spare people to review the backlog very often). |
@d3r3kk and/or @junyzheng - are we seeing this internally? |
Yep this is a dupe of the above issue already raised at infra so this can be closed. I forgot to exclude the test which is why it still appears in the nightlies. |
It appears the jdk_native_sanity test on Windows passes on godaddy machines but fails on azure machines - see https://trss.adoptopenjdk.net/deepHistory?testId=5ddd0fd4440f9a5cbaaf02d5.
The text was updated successfully, but these errors were encountered: