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

Increment Windows cache URL #6321

Merged
merged 1 commit into from
Jun 12, 2020
Merged

Increment Windows cache URL #6321

merged 1 commit into from
Jun 12, 2020

Conversation

aherrmann-da
Copy link
Contributor

We've seen a series of failures of the form

ERROR: D:/a/1/s/daml-assistant/integration-tests/BUILD.bazel:162:1: output 'daml-assistant/integration-tests/create-daml-app-tests.exe' was not created
ERROR: D:/a/1/s/daml-assistant/integration-tests/BUILD.bazel:162:1: not all outputs were created or valid

across multiple machines. We suspect cache poisoning as the cause. This
increments the cache URL to effectively clear the cache.

See #6262

Pull Request Checklist

  • Read and understand the contribution guidelines
  • Include appropriate tests
  • Set a descriptive title and thorough description
  • Add a reference to the issue this PR will solve, if appropriate
  • Include changelog additions in one or more commit message bodies between the CHANGELOG_BEGIN and CHANGELOG_END tags
  • Normal production system change, include purpose of change in description

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.

We've seen a series of failures of the form
```
ERROR: D:/a/1/s/daml-assistant/integration-tests/BUILD.bazel:162:1: output 'daml-assistant/integration-tests/create-daml-app-tests.exe' was not created
ERROR: D:/a/1/s/daml-assistant/integration-tests/BUILD.bazel:162:1: not all outputs were created or valid
```
across multiple machines. We suspect cache poisoning as the cause. This
increments the cache URL to effectively clear the cache.

changelog_begin
changelog_end
@@ -37,6 +37,7 @@ function bazel() {


bazel shutdown
bazel clean --expunge
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you want to merge the clean --expunge? I guess in this case, that’s the only option since it doesn’t just affect the compat node which we can reset fairly easily.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, and then remove it after the nodes were reset. To avoid poisoning the fresh cache with broken items in the local cache of some nodes.

@cocreature cocreature merged commit d1e4225 into master Jun 12, 2020
@cocreature cocreature deleted the bump-windows-cache branch June 12, 2020 13:33
@garyverhaegen-da
Copy link
Contributor

All nodes have been reset.

garyverhaegen-da added a commit that referenced this pull request Jun 12, 2020
See #6321

CHANGELOG_BEGIN
CHANGELOG_END
garyverhaegen-da added a commit that referenced this pull request Jun 12, 2020
See #6321

CHANGELOG_BEGIN
CHANGELOG_END
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.

4 participants