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

Always build non-cached generators in work_root #713

Closed
wants to merge 1 commit into from
Closed

Conversation

olofk
Copy link
Owner

@olofk olofk commented Dec 20, 2024

Before this change, non-cached generators were only built in work_root if --no-export was enabled which caused race conditions when doing multiple parallel builds.

With this change we also don't remove the temporary generator work directory as that can be useful to have around and will be cleaned out on subsequent builds to the same work_root anyway.

Before this change, non-cached generators were only built in work_root
if --no-export was enabled which caused race conditions when doing
multiple parallel builds.

With this change we also don't remove the temporary generator work
directory as that can be useful to have around and will be cleaned
out on subsequent builds to the same work_root anyway.
@a-will
Copy link
Contributor

a-will commented Dec 23, 2024

Looks good to me! If it isn't there already, I'd recommend adding a comment in docs somewhere stating that a work_root should not be shared across multiple simultaneous fusesoc processes.

@olofk
Copy link
Owner Author

olofk commented Dec 28, 2024

Great. I can add the clarification about work root, but I was assuming that all kinds of things already broke if you tried to use the same work root with different processes. Out of curiosity, is this something you are using?

@a-will
Copy link
Contributor

a-will commented Dec 28, 2024

Great. I can add the clarification about work root, but I was assuming that all kinds of things already broke if you tried to use the same work root with different processes. Out of curiosity, is this something you are using?

No, or at least not that I am aware of!

I was merely suggesting offering clarity to users about fusesoc's limits. Unlike bazel, for example, fusesoc does not prevent the user from attempting to share a work_root, even if might only happen by accident.

@olofk
Copy link
Owner Author

olofk commented Jan 7, 2025

Docs updated now. Closing this.

@olofk olofk closed this Jan 7, 2025
@olofk olofk deleted the cachedir branch January 8, 2025 08:37
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

Successfully merging this pull request may close these issues.

2 participants