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

Prevent false remote cache hits between builds on different operating systems #13552

Closed
jamiesnape opened this issue Jun 12, 2020 · 4 comments
Closed
Labels
component: continuous integration Jenkins, CDash, mirroring of externals, website infrastructure priority: medium unused team: kitware

Comments

@jamiesnape
Copy link
Contributor

Relates #13102.

Per bazelbuild/bazel#4558 and bazelbuild/bazel#3320 seems creating separate caches is the only truly safe solution.

@jamiesnape jamiesnape added unused team: kitware component: continuous integration Jenkins, CDash, mirroring of externals, website infrastructure priority: medium labels Jun 12, 2020
@jamiesnape jamiesnape self-assigned this Jun 12, 2020
@jamiesnape
Copy link
Contributor Author

A minimal set of tools for a cache key would be:

  • CC (clang or gcc)
  • gfortran
  • java
  • python3

Something like

dpkg-query --showformat='${Version}' --show $(dpkg-query --search $(readlink -f $(command -v ${tool_name})) | cut -d':' -f1)

will get the version in a non-tool-specific way on Ubuntu (modulo some double quotes).

@jwnimmer-tri
Copy link
Collaborator

Is this a blocker for #13434?

@jamiesnape
Copy link
Contributor Author

Pretty much. It is not a difficult task, though.

@jamiesnape
Copy link
Contributor Author

Closed by RobotLocomotion/drake-ci@7a41cae.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: continuous integration Jenkins, CDash, mirroring of externals, website infrastructure priority: medium unused team: kitware
Development

No branches or pull requests

2 participants