Temporarily disable docker caching via cargo-chef #643
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unfortunately cargo-chef no longer seems to work for this repository; it complains about a missing 'inherits' directive for the CI profile, even though it is not actually missing. Additionally, downgrading to previous versions also somehow causes errors.
Removing the CI profile fixes the docker build, however, since the scene detection is too slow for the CI in the debug build, and since we still would like overflow checking and debug assertions (and hence can't use the release profile), removing the CI profile is not a feasible workaround for this issue.
Therefore, the only solution for now seems to be to disable cargo-chef altogether, as being able to build via docker is preferable to being unable to do so at all, even if it is not as fast as it could be with docker layer caching.