-
Notifications
You must be signed in to change notification settings - Fork 205
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
Fix concurrent DAML compilations on Windows #679
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, but doesn't this litter a million temp dirs on Windows? Would it not be better to chose a name uniquely based on the result name?
34371af
to
07f9160
Compare
Good point, I’ve changed it to reuse the same directory name. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A more enthusiastic approval this time around
tar xf {db_tar} -C tmp_db --strip-components 1 | ||
mkdir -p tmp_db/{daml_lf_version} | ||
PACKAGEDB="package_db_for_{name}" | ||
# Since we don’t have sandboxing on Windows, that directory might |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Since we don’t have sandboxing on Windows, that directory might | |
# Since we don't have sandboxing on Windows, that directory might |
Smart quotes seem like a terrible idea here
991fd2b
to
b3e7ac0
Compare
b3e7ac0
to
2cb6a67
Compare
Since Windows builds aren’t sandboxed properly (see bazelbuild/bazel#5136), concurrent compilations interact with the same tmp_db directory which leads to flaky build failures.
2cb6a67
to
291296d
Compare
Since Windows builds aren’t sandboxed properly (see
bazelbuild/bazel#5136), concurrent
compilations interact with the same tmp_db directory which leads to
flaky build failures.
Pull Request Checklist
NOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.