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

Avoid permissions conflict on shared protocjar.webcache #774

Merged
merged 2 commits into from
Jan 31, 2021

Conversation

jerryz123
Copy link
Contributor

The Java protoc plugin (part of FIRRTL) by default caches protoc in /tmp, and does not delete it afterwards.
This causes permissions failures when multiple users try to install Chipyard on the same machine, due to permissions failures over accessing the same cache in /tmp.

A solution is to place the tmpdir within the Chipyard repo. No other files besides protocjar.webcache currently use that directory, so I believe this should be safe.

Type of change: bug fix

Impact: software change

The Java protoc plugin (part of FIRRTL) by default caches protoc in /tmp, and does not delete it afterwards.
This causes permissions failures when multiple users try to install Chipyard on the same machine, due to permissions failures over accessing the same cache in /tmp.

A solution is to place the tmpdir within the Chipyard repo. No other files besides protocjar.webcache currently use that directory, so I believe this should be safe.
@abejgonzalez
Copy link
Contributor

Doesn't this require you to make the folder beforehand (before the first time GenerateSimFiles is run)?

@jerryz123
Copy link
Contributor Author

Oh yeah, I need to check in that directory as well

Copy link
Contributor

@abejgonzalez abejgonzalez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we want to enforce this on every user since this seems like a very UCB problem. Maybe we should add some documentation/issue pointing to this fix? With that being said, I think for now we can use this and if someone wants this removed we can revisit it (#agile-dev).

@jerryz123 jerryz123 merged commit 255452f into dev Jan 31, 2021
@jerryz123 jerryz123 deleted the jerryz123-patch-1 branch February 18, 2021 20:42
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