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

test-softlayer-win2012r2-x64-1 I/O problems #1404

Closed
andrew-m-leonard opened this issue Jun 22, 2020 · 4 comments
Closed

test-softlayer-win2012r2-x64-1 I/O problems #1404

andrew-m-leonard opened this issue Jun 22, 2020 · 4 comments
Assignees
Labels
Milestone

Comments

@andrew-m-leonard
Copy link
Contributor

Test_openjdk14_j9_sanity.openjdk_x86-64_windows:
https://ci.adoptopenjdk.net/job/Test_openjdk14_j9_sanity.openjdk_x86-64_windows/112/console

ERROR: Failed to clean the workspace
jenkins.util.io.CompositeIOException: Unable to delete 'C:\Users\jenkins\workspace\Test_openjdk14_j9_sanity.openjdk_x86-64_windows\openjdk-tests'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
@karianna
Copy link
Contributor

@Willsparker - I wonder if we're seeing a cygwin bug here as well. How old are the Cygwins on those machines?

@Willsparker
Copy link
Contributor

ref: #1396

@karianna I think it's due to leftover processes. When I try and delete it using file explorer (as Admin), I get this:
Screenshot 2020-06-22 at 13 46 18

When I go through resource monitor, I can see there's still some java processes running on it:
Screenshot 2020-06-22 at 13 48 54

Once I end the Java processes manually, I'm able to delete the file.

The version this machine is running (according to uname -r in the Cygwin terminal) is 3.1.5(0.340/5/3), which I believe is the latest version of cygwin (https://www.cygwin.com/)

@Willsparker
Copy link
Contributor

I suppose it could be a Cygwin issue, however, Jenkins is meant to have a way of auto killing any process that is spawned within a job (see https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller ), so unless Cygwin escapes that somehow, this shouldn't happen.. :/

@Willsparker Willsparker self-assigned this Jun 22, 2020
@Willsparker
Copy link
Contributor

I'm going to close this issue as the workspace has been cleared now - We have #1396 to track how to possibly fix it :-)

infrastructure automation moved this from TODO to Done Jun 22, 2020
@karianna karianna added this to the June 2020 milestone Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

3 participants