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
Currently the CI uses the oqs-arm64 runner, this is a "self-hosted" runner leveraging the not yet public GitHub-hosted arm64 runner (blog). According to github/roadmap#970 the arm64 runner should be available in Q1. Once the runner is public we will want to switch our CI from oqs-arm54 to the new arm64 runner, this will address the fact that the CI running on forks will be left in queued forever.
Once the runner is release this should be a simple find and replace with the runner name.
The text was updated successfully, but these errors were encountered:
Currently the CI uses the
oqs-arm64
runner, this is a "self-hosted" runner leveraging the not yet public GitHub-hosted arm64 runner (blog). According to github/roadmap#970 the arm64 runner should be available in Q1. Once the runner is public we will want to switch our CI fromoqs-arm54
to the newarm64
runner, this will address the fact that the CI running on forks will be left in queued forever.Once the runner is release this should be a simple find and replace with the runner name.
The text was updated successfully, but these errors were encountered: