Reenable git-daemon journey tests on CI by disabling artifact caching #1725
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.
Running journey tests that use
git-daemon
broke in thetest-journey
CI job since #1634 for unknown reasons, and they were disabled in 9566488, as discussed in #1634 (review).This reenables those journey tests on CI, and fixes them by disabling the
rust-cache
step that caches compiled artifacts. It's rather odd that this works, but it very much does seem to.See #1634 (comment) for full details on this in a broader context, as well as other things I've tried and why none of the other things I've tried are ready to go yet.
I view this as a workaround rather than full-blown fix, but it seems to me that it's worth doing as a way to let those tests run on CI in a way that doesn't break anything else. With caching turned off, the
test-journey
job takes up to about 6:30 to finish; it seems to me that this may be acceptable even if not ideal, given the significantly greater running time of some of the other jobs.This is, of course, only turning off artifact caching for the
test-journey
job, not for any other jobs.