CircleCI failing on main #318
Assignees
Comments
Merged
I can open a PR for this today, I'll be out tomorrow and Friday though.
Based on this I will fix the previously working CI, I already found the typo in the httpd job) and re-disable the failing jobs that were previously failing (openvpn, ngtcp2, and h2load). |
ajbozarth
added a commit
to ajbozarth/oqs-demos
that referenced
this issue
Nov 20, 2024
This fixes a typo in the httpd job and disables the failing openvpn, ngtcp2, and h2load jobs that were re-enabled in open-quantum-safe#298 Fixes open-quantum-safe#318 Signed-off-by: Alex Bozarth <[email protected]>
baentsch
pushed a commit
that referenced
this issue
Nov 21, 2024
This fixes a typo in the httpd job and disables the failing openvpn, ngtcp2, and h2load jobs that were re-enabled in #298 Fixes #318 Signed-off-by: Alex Bozarth <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#298 introduced CI failures and triggered CCI-related ones. This issue is to track resolving them.
Question to @ajbozarth whether you have bandwidth to do this or whether you're indeed away?
Given the problems are CCI ones and you volunteered to take on #294, I'm tempted to simply disable CircleCI until you (or anyone else) get(s) around to doing this. Objections anyone? Implications: No new docker images (beyond the oqs-provider and quic ones already on GH CI) will be pushed until then.
The text was updated successfully, but these errors were encountered: