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

Fix concurrent DAML compilations on Windows #679

Merged
merged 1 commit into from
Apr 24, 2019
Merged

Conversation

cocreature
Copy link
Contributor

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 to
trigger the build.

Copy link
Contributor

@aherrmann aherrmann left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@neil-da neil-da left a 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?

@cocreature
Copy link
Contributor Author

Good point, I’ve changed it to reuse the same directory name.

Copy link
Contributor

@neil-da neil-da left a 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
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
# Since we dont 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

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.
@mergify mergify bot merged commit 16d82f6 into master Apr 24, 2019
@mergify mergify bot deleted the tmp-package-db branch April 24, 2019 22:47
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.

3 participants