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

"Failed to save cached analysis" error #251

Open
joprice opened this issue Dec 10, 2019 · 5 comments
Open

"Failed to save cached analysis" error #251

joprice opened this issue Dec 10, 2019 · 5 comments

Comments

@joprice
Copy link
Contributor

joprice commented Dec 10, 2019

On some builds, I get a an error like Failed to save cached analysis: java.nio.file.NoSuchFileException: service/.tmp. The error does not give any specific reason for the failure, so I'm not sure where to begin debugging.

@SrodriguezO
Copy link
Collaborator

SrodriguezO commented Dec 10, 2019

Hey @joprice, the error's happening when the Zinc runner tries to save the Zinc state files when persistent builds are enabled. Is there a stack trace in the output you're seeing? Also, are you seeing this error consistently? (i.e. if you build and get the error, clean, and then build again, do you still get the error?)

@joprice
Copy link
Contributor Author

joprice commented Dec 12, 2019

There was no stacktrace, and it only happens intermittently and doesn't seem to affect the build.

@joprice
Copy link
Contributor Author

joprice commented Dec 12, 2019

I'll try to capture more info if it pops up again.

@pauldraper
Copy link
Contributor

The error comes from here.

It most likely originates here.

Immediately before it, we create the service directory (or whatever the target's name is).

So either the file system is behaving inconsistently, or there are multiple instances running in that directory. Since Bazel runs only one build at a time, there should not be multiple instances. Unless if after sanitation there is a collision.

@joprice
Copy link
Contributor Author

joprice commented Jan 21, 2020

I haven't seen this since, so feel free to close if it's not helpful to track it down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants