Skip to content

[CI] integTestCluster#wait fails on Windows #29992

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

Closed
elasticmachine opened this issue Mar 26, 2018 · 4 comments
Closed

[CI] integTestCluster#wait fails on Windows #29992

elasticmachine opened this issue Mar 26, 2018 · 4 comments
Assignees
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticmachine
Copy link
Collaborator

Original comment by @DaveCTurner:

LINK REDACTED

LINK REDACTED

LINK REDACTED

All of the above failed in a relatively short time with the message

Execution failed for task ':x-pack-elasticsearch:plugin:integTestCluster#wait'.

I'm afraid the logs are not very meaningful to me. The first bad-looking message seems to be

|    ERROR: Temporary file directory [C:\Users\JENKIN~1.WOR\AppData\Local\Temp\elasticsearch] does not exist or is not accessible

This is strange as this directory seems to exist and be accessible to the Jenkins service user.

@elasticmachine
Copy link
Collaborator Author

Original comment by @droberts195:

The error message is the one that was added in #28217.

If this error had occurred on every Windows build since that PR was merged then I'd say this issue was a blocker for release of 6.3. However, quite a few Windows CI builds have succeeded since then, and this particular problem has only occurred repeatedly in the last day or so. The working directory for the tests in CI has been changed recently, so it could be related to that. If the temp directory is being created in parallel with running Elasticsearch then the new check is doing its job and the fix will be to change the CI setup.

I will investigate further.

@elasticmachine
Copy link
Collaborator Author

Original comment by @droberts195:

I had a look to see if this is still happening and the build after the most recent failure listed in the description succeeded:

LINK REDACTED

However, two builds later this Jenkins job started failing due to being unable to find Java. Then that was fixed, but all subsequent builds failed due to being unable to find Git.

I raised LINK REDACTED to get the current problem with Git resolved. Once that's done I'll check whether the temp directory is a problem again. But it's clear that there's been considerable churn in the scripts used to set up the Jenkins workers recently, and hopefully that was the reason behind the failure this issue was raised for rather than some problem with the Java code.

@elasticmachine elasticmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Apr 25, 2018
@jasontedor
Copy link
Member

Relates #30325

@jasontedor
Copy link
Member

This does not appear to be happening anymore.

@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants