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

Disable cache for install_pkgs_reproducibility_test deps #2071

Closed

Conversation

laurynaslubys
Copy link
Contributor

@laurynaslubys laurynaslubys commented Apr 25, 2022

Docker rules are not hermetic as the sha of layers depends on the modification times of files inside containers.
If the the containers get cached from different runs, they will have different sha sums.

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Some PRs (#1439 #2068) are blocked on //tests/docker/package_managers:install_pkgs_reproducibility_test failing.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

download_pkgs is not hermetic as it goes out to the package repository to fetch packages.
If the remote apt repository gets updated, the bazel cache can get into a weird state.
@laurynaslubys
Copy link
Contributor Author

This may have accidentally been caused by #2043

@laurynaslubys laurynaslubys changed the title Pin version of git used install_pkgs_reproducibility_test Disable cache for install_pkgs_reproducibility_test deps Apr 25, 2022
@github-actions
Copy link

This Pull Request has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!

@github-actions github-actions bot added the Can Close? Will close in 30 days unless there is a comment indicating why not label Oct 23, 2022
@github-actions
Copy link

This PR was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"

@github-actions github-actions bot closed this Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Can Close? Will close in 30 days unless there is a comment indicating why not
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant