You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Jared, thanks for setting up the CI!
I noticed the following issue: it succeeds on commit 4b8aa79 but fails on commit 53a61e6. The only different is that caching is disabled in the former.
The text was updated successfully, but these errors were encountered:
I ran into the same issue on branch fix-keygen-patch, where caching is disabled. So it's something else, which seems exacerbated by caching. Last time, when I tried to diagnose it, I used https://github.com/mxschmitt/action-tmate to get a shell right before docker-compose run blst, and the problem didn't show up in the interactive shell...
I just ran into this exact same problem while trying to run docker-compose build in a local clone of the blst-verification repo. A fix along the lines of GaloisInc/saw-script#1107 might be in order.
Okay, so if I understand correctly, the fix is to always prepend "apt-get update && " to any "apt-get install" command, in order to make sure it's not using a stale apt cache.
Hi Jared, thanks for setting up the CI!
I noticed the following issue: it succeeds on commit 4b8aa79 but fails on commit 53a61e6. The only different is that caching is disabled in the former.
The text was updated successfully, but these errors were encountered: