-
Notifications
You must be signed in to change notification settings - Fork 731
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
sanity.openjdk Windows IOException: Access is denied #8374
Comments
@smlambert @llxia seems like a setup issue, any ideas? |
Sorry, I do not recall any special settings for openjdk tests on windows. @sophia-guo do you have any ideas? |
Yes, looks like the setup issue. No same issue happened in AdoptOpenJDK windows test builds. The most errors are either calling
In adopt the jenkins windows TEMP is set as:
What's the %TEMP% in those Eclipse openj9 windows? ( looks like it's %systemdrive%\Windows\Temp ) |
@jdekonin can you please address the previous comment. |
The machines are all the same. There is no restriction on jobs writing to /tmp. Where is the job trying to write too? Why is the job trying to create content outside of the workspace directory? This leads to content clutter on the machines.
|
Test job with createTempFile creates an empty file in the default temporary-file directory ( note it is jenkins user on cygwin). There are some other access denied
Test could cleans up itself when exit( f.deleteOnExit(); ), which is independent of jenkins job. Shouldn't have leftover issue. If not should report an issue in JBS. |
We run Looking at a passing run on a windows machines at AdoptOpenJDK, there is both a TMP and TEMP environment variable set. Looking at the console output of the failing test on the OpenJ9 machine, there is no TMP or TEMP environment variables. That seems to be the fundamental difference between machine configurations that is causing the test failure. If you compare all printenv output, you also see other differences between environment variables, including between PATH settings. If you correct this difference in machine configuration, the test failures will be resolved. |
@jdekonin fyi Shelley's comment #8374 (comment) |
Machines are connecting to jenkins differently, otherwise I don't see anything playbook specific that would address the setting of the env. TEMP is now defined in the machine configuration. Pete launched a grinder to see what else fails. Just jdk_security1_0, any suggestions as to what is needed if this is a system configuration issue?
|
Make env vars stick in jenkins config |
Updated the jdk_security1_0 failure comment with more information, although still not helpful. It's using the MSCAPI Provider, which is Windows specific. Googling found https://docs.genesys.com/Documentation/PSDK/latest/Developer/TLSSecurityProviders which mentions certmgr.msc, not sure if that helps. |
@vsebe is this something that you have seen with any of our internal windows test wrt machine configuration requirements? |
Nothing related to certificates in WMI. |
The IOException no longer occurs. https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.openjdk_x86-32_windows_Personal/2 I've created a new Issue for the jdk_security1_0 failures. |
https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.openjdk_x86-32_windows_Personal/1
https://ci.eclipse.org/openj9/job/Test_openjdk8_j9_sanity.openjdk_x86-64_windows_Personal/1
All tests fail with
IOException: Access is denied
The text was updated successfully, but these errors were encountered: