Open ee7 opened 3 years ago
The archive has been replaced with a working one (see https://api.github.com/repos/nim-lang/nightlies/releases/36527859 and Ctrl+f for updated_at
).
@alaviss Do we know why the archive was broken? Can we add a check to the release process so that this can't happen again?
I'm not sure, the said build passed with no noticeable errors: https://github.com/nim-lang/nightlies/runs/1718858154?check_suite_focus=true
My guess is that there were some issues with Github's server during the upload to latest-version-1-4
, since only the linux 64bit tarball was broken.
Is it possible/sensible to add a step/job that downloads the archives and checks that they extract without error? Or that they match an expected hash?
Sure, but overuse of the Github APIs will get us throttled, which I want to avoid. We can already trip this by having two nightlies run consecutively in one day (due to a Nim minor release for example).
Frankly I would want to get #49 fixed so we don't have to do double uploads.
The latest 1.4
linux_x64.tar.xz
archive is corrupt.The release page is here: https://github.com/nim-lang/nightlies/releases/tag/latest-version-1-4
Example
Current behaviour
Expected behaviour
No error.
Additional information
It looks like this doesn't affect the other
latest-version-1-4
archives.This issue means that people using
version-1-4
with thealaviss/setup-nim
action will see CI failures:The release page contains
This seems to be false - they're built from different commits, and the x64 linux archive on the linked
2021-01-03
page is not corrupt: