-
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
Unexpected ##[error]read ECONNRESET #35
Comments
The link to the log doesn't work properly, it sends me to the Action tab, where it doesn't show any failing jobs. Maybe I should just wrap all the downloads in a loop that tries a few times if it fails. |
Sorry! I guess it got removed after doing a rebase. It was a one-time thing, without any further log or messages. |
That's a good idea! Could you also integrate this to setup-julia? so we don't need to write it in our workflows? - name: Cache artifacts
uses: actions/cache@v1
env:
cache-name: cache-artifacts
with:
path: ~/.julia/artifacts
key: ${{ runner.os }}-test-${{ env.cache-name }}-${{ hashFiles('**/Project.toml') }}
restore-keys: |
${{ runner.os }}-test-${{ env.cache-name }}-
${{ runner.os }}-test-
${{ runner.os }}- |
They only recently added the SDKs to interact with the cache from actions rather than workflows. It's on my list but I haven't had the time yet. |
The error happened to me again. I am pasting the whole log so you can fix it: Details
|
Hm, I have no idea what could cause it, but I'll add a retry-loop I guess |
I've been seeing this very occasionally. I think it's just flaky network on GitHub's part. Maybe a bounded retry loop? With e.g. a maximum of 3 tries? |
@SaschaMann What do you think of adding a bounded retry loop? I'm still seeing this error intermittently, e.g. https://github.com/simonbyrne/KeywordDispatch.jl/runs/1692480701 |
Hopefully #70 fixed this but please let me know if you still encounter the error. |
https://github.com/timholy/SnoopCompile.jl/pull/107/checks?check_run_id=804747167
The text was updated successfully, but these errors were encountered: