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.

Sign up for GitHub

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

Jump to bottom

CI: Docker Windows Test can’t clean up workspace #10903

Closed
medyagh opened this issue Mar 23, 2021 · 1 comment
Closed

CI: Docker Windows Test can’t clean up workspace #10903

medyagh opened this issue Mar 23, 2021 · 1 comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/process Process oriented issues, like setting up CI priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@medyagh
Copy link
Member

medyagh commented Mar 23, 2021

As seen in https://storage.googleapis.com/minikube-builds/logs/10722/cc7973a/Docker_Windows.txt

Started by upstream project "Build_Cross" build number 17423
originally caused by:
 GitHub pull request #10722 of commit cc7973a00f9289dd673b468d82164735e184081b, no merge conflicts.
Running as SYSTEM
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Evaluating the Groovy script content
[EnvInject] - Injecting contributions.
Building remotely on GCP Windows Agent 3 (windows-docker) in workspace C:\jenkins\workspace\Docker_Windows_integration
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\jenkins\workspace\Docker_Windows_integration'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
ERROR: Cannot delete workspace: Unable to delete 'C:\jenkins\workspace\Docker_Windows_integration'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
@medyagh medyagh added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/process Process oriented issues, like setting up CI priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 23, 2021
@sharifelgamal
Copy link
Collaborator

This issue seems to be specific to one of the windows CI machines, it has been taken down and tests are now running properly. I'll fix that machine up and bring it back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/process Process oriented issues, like setting up CI priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@medyagh @sharifelgamal