GitHub Actions: on self-hosted runners, we need to check if Julia is available in the PATH, and install it if needed
#429
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
…available in the `PATH`, and install it if needed
|
bors merge |
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.
which juliastep will always succeed, and so we will never spend any time install Julia on GitHub-hosted runners.which juliawill fail every time, so we will run thesetup-juliaaction every time. However, this does not mean that we need to spend time installing Julia every time. The first time, the toolcache (e.g./runner/_work/_tool) will be cold, so we will need to download and install Julia. But every subsequent time that we run thesetup-juliaaction, the toolcache will be warm, and so running thesetup-juliaaction will essentially be a no-op.