Conversation
No need to be overly generic.
The tests use transitions to test multiple Zig versions, so the CI matrix is not needed on that axis. The Bazel version should not be relevant, so the test is limited to the latest Bazel version.
That Zig version specifically is failing local builds with ``` error: unable to open directory '/var/tmp/zig-cache/b/1f12c83657f1b28979d409d11f49642c/': FileNotFound ```
This file contains hidden or 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.
Zig docs builds frequently failed on CI, see #273. Two cases were observed:
The first case is addressed by moving Zig docs build tests into a separate CI job and disabling remote execution in that case.
The second case is addressed by marking Zig docs targets as incompatible with Zig version 0.12.0 and MacOS systems.
This is a workaround, not a proper fix of #273.