-
Notifications
You must be signed in to change notification settings - Fork 729
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 cannot delete workspace #17175
Comments
Both
I am not sure why the owner is |
Looked a bit. No idea why that file got re-owned. I ran the sanitize job, which does a reboot. Then I was able to rm the DIR. If there are more I suspect they will clean themselves up eventually with the automated cleanups. Doesn't help the test builds from failing though. I wonder if the test pipelines should be updated to not fail if cleanup fails? Or perhaps just on Windows? But maybe that is sweeping more issues under the rug. |
It's just on Windows and has been happening often lately, I suspect it's a real issue that needs to be fixed. |
Do you also see Here is what I noticed cleanWs worked at the beginning of the above extended.functional test build, which means
If the jars are downloaded on demand, the functional test build will not download Is it possible something happened during copyArtifacts. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.system_x86-64_windows_Nightly_testList_1/514 |
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_x86-64_windows_Personal_testList_0/135
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_1/38
|
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.system_x86-32_windows_Nightly_testList_0/513
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_extended.functional_x86-64_windows_Nightly_testList_0/147
|
It's also interesting it does nothing for 2 hours when there is a problem. |
A different failure type, perhaps related. https://openj9-jenkins.osuosl.org/job/Test_openjdk20_j9_sanity.openjdk_x86-64_windows_Nightly/39
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_x86-64_windows_Personal/138
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_special.system_x86-64_windows_Personal_testList_1/68
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_extended.functional_x86-32_windows_Nightly_testList_1/517 https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.system_x86-32_windows_Nightly_testList_0/517 This one is different, caused by the MauveMultiThrdLoad_5m_2 test failure, which seems machine problem. |
This one never ran any testing, I guess it's trying to delete the workspace first. https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.functional_x86-64_windows_Nightly/525 I do see
|
Seems related
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.system_x86-64_windows_Nightly_testList_1/471 |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_windows_Release/62 |
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.openjdk_x86-32_windows_Nightly/532 https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_x86-64_windows_Nightly_testList_1/472/ https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.system_x86-64_windows_Nightly_testList_0/472 https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.system_x86-64_windows_Nightly_testList_1/472/ |
I wonder if we can add some debug in the test pipeline code
|
There doesn't seem a benefit for me to keep reporting the failures, I will start ignoring them. https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.system_x86-32_windows_Nightly_testList_0/526 |
fyi @llxia still happening
|
As we updated the logic to pre-stage 3rd party libs on the machines (adoptium/aqa-tests#4500), this issue should be resolved. Please reopen if this occurs again. |
I've seen quite a few "Cannot delete workspace" errors in the last while. Looking at the latest
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_windows_Nightly/460/console
@llxia
The text was updated successfully, but these errors were encountered: