AppVeyor: Timeout before deleting Gradle lock file #1231
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
And re-enable the Gradle daemon.
|
And when I went digging I saw Artur had commented on a YouTrack issue so this has been happening intermittently for some time: https://youtrack.jetbrains.com/issue/KT-18300 Skipping deletion of the lock file entirely won't help either. The error happens before the caching occurs. I'm wondering if the caching be left as is, this PR closed, and if someone knows how to avoid the error coming up they raise a PR to address it. Flaky builds are awful though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
And re-enable the Gradle daemon.
(Hopefully) fixes #1230 finally leading to reliable builds on AppVeyor.
I did manage to replicate this problem locally - seems that the process the daemon spawns when running a task is not cleaned up before the daemon itself shuts down. Whether that's a bug in Gradle or in one of the components used when the task runs is unclear, but hopefully this works around it.
If not we'll do option 3 and move on with our lives.