-
Notifications
You must be signed in to change notification settings - Fork 23
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
Setup fails on persistent runner when julia version updates #32
Comments
Thanks for reporting this issue. I didn't know persistent build environments are even a thing :D The 2nd suggestion sounds good to me, I'll implement it over the weekend. |
It'll take a bit longer. I want to add some checks that the correct version is in the path even when multiple versions of Julia are installed but I have to read up on how the testing framework actions use works to do it properly. |
Sorry, I haven't had enough time to finish it yet, so the next Julia update will break it once more. I'm still trying to understand the test framework and I'm a bit hesitant to change the install directory if I can't test it well because that could break hundreds of builds. |
Sorry that it took me a lot longer, #46 should fix it. I misused tool-cache before and effectively had two locations where Julia was installed. GitHub's tool-cache will handle the directories, as it has before, and Julia will be installed in
I don't have access to a self-hosted runner, so please let me know if this works once the next Julia version comes out. |
Thanks! It's actually super easy to set up your local machine as a self hosted runner, if you wanted to try it out. I'll give it a go with ours and report back |
I have a self-hosted runner that persists between runs, which usually works with the setup-julia step.
However, when the julia version updates I get:
I guess there are two options:
/julia
dir before upgrade/julia1.4.2
dirs, but point a symlink fromjulia
to the requested versionThe text was updated successfully, but these errors were encountered: