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

Jenkins master build failed at grpc-jenkins-windows-worker3 FileSystemException #3877

Closed
stanley-cheung opened this issue Oct 19, 2015 · 7 comments
Assignees
Labels
disposition/BUILDNURSE For all buildnurse related build/test failures and flakes infra/Jenkins platform/Windows

Comments

@stanley-cheung
Copy link
Contributor

The last relatively green master build is https://grpc-testing.appspot.com/job/gRPC_master/8345/ at Oct 15, 2015 8:42:01 PM (since last Thursday night, about 4 days ago). Ever since then (8346 and onward), all the master builds are failing at the very top with this stack trace

Started by timer
Building remotely on grpc-jenkins-windows-worker3 (x86_64 i386 windows) in workspace c:\jenkins\workspace\gRPC_master
Wiping out workspace first.
java.io.IOException: remote file operation failed: c:\jenkins\workspace\gRPC_master at hudson.remoting.Channel@6877b8a3:grpc-jenkins-windows-worker3: java.nio.file.FileSystemException: c:\jenkins\workspace\gRPC_master\config\dbg\language\c\platform\windows: The process cannot access the file because it is being used by another process.

    at hudson.FilePath.act(FilePath.java:987)
    at hudson.FilePath.act(FilePath.java:969)
    at hudson.FilePath.deleteContents(FilePath.java:1184)
    at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28)
    at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1040)
    at hudson.scm.SCM.checkout(SCM.java:485)
    at hudson.model.AbstractProject.checkout(AbstractProject.java:1277)
    at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
    at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
    at hudson.model.Run.execute(Run.java:1741)
    at hudson.matrix.MatrixBuild.run(MatrixBuild.java:301)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:408)
Caused by: java.nio.file.FileSystemException: c:\jenkins\workspace\gRPC_master\config\dbg\language\c\platform\windows: The process cannot access the file because it is being used by another process.

    at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
    at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
    at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
    at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
    at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source)
@stanley-cheung stanley-cheung added infra/Jenkins disposition/BUILDNURSE For all buildnurse related build/test failures and flakes labels Oct 19, 2015
@stanley-cheung stanley-cheung added this to the GA milestone Oct 19, 2015
@stanley-cheung
Copy link
Contributor Author

I tried to log into the instance but couldn't quite figure out what process is locking that file

@stanley-cheung
Copy link
Contributor Author

I restarted the instance grpc-jenkins-windows-worker3 and looked like the problem goes away. But the issue could come back in the future.

@stanley-cheung stanley-cheung changed the title Jenkins master build is failing at the top Jenkins master build failed at grpc-jenkins-windows-worker3 FileSystemException Oct 20, 2015
@stanley-cheung
Copy link
Contributor Author

@stanley-cheung
Copy link
Contributor Author

This thread seems relevant: https://issues.jenkins-ci.org/browse/JENKINS-19994. One suggestion in the middle of the thread is to disable the "Wipe out repository & force clone" options in the project configuration.

@yang-g
Copy link
Member

yang-g commented Oct 21, 2015

Seen this again today~

@stanley-cheung
Copy link
Contributor Author

I don't know what was done but this seems to not happen anymore. When a build failed now it's most likely due to #3724.

Edit: could just be because the master worker so happened to be not grpc-jenkins-windows-worker3

@jtattermusch
Copy link
Contributor

Doesn't look like we're seeing this anymore. Closing this as part of buildpony bankruptcy.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
disposition/BUILDNURSE For all buildnurse related build/test failures and flakes infra/Jenkins platform/Windows
Projects
None yet
Development

No branches or pull requests

5 participants