Skip to content

PQC: Add TLS 1.3 groups for (pure) ML-KEM-512, -768 and -1024 #6167

PQC: Add TLS 1.3 groups for (pure) ML-KEM-512, -768 and -1024

PQC: Add TLS 1.3 groups for (pure) ML-KEM-512, -768 and -1024 #6167

Triggered via pull request October 18, 2024 09:51
Status Cancelled
Total duration 4m 3s
Artifacts

ci.yml

on: pull_request
Matrix: Analysis
Matrix: Linux
Matrix: macOS
Matrix: Special
Matrix: Windows
Matrix: Cross
Fit to window
Zoom out
Zoom in

Annotations

38 errors and 6 warnings
Windows (static, x86_64, windows-2022)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (sanitizer, clang, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (limbo, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (valgrind, clang, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (lint, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Special (docs, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Special (examples, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Special (bsi, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Special (no_pcurves, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Special (minimized, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-android-arm64, clang, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-arm32, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-i386, gcc, ubuntu-22.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-mips64, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-ios-arm64, xcode, macos-13)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-ppc64, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (cross-arm64, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Cross (static, gcc, windows-2022, make)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Windows (shared, x86, windows-2022)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Windows (shared, x86_64, windows-2022)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
macOS (amalgamation, xcode, macos-13)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Linux (gcc, amalgamation)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Linux (gcc, amalgamation)
The operation was canceled.
Analysis (fuzzers, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (fuzzers, gcc, ubuntu-24.04)
The operation was canceled.
macOS (amalgamation, xcode, macos-14)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
macOS (amalgamation, xcode, macos-14)
The operation was canceled.
Linux (gcc, shared)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Linux (gcc, shared)
The operation was canceled.
Analysis (coverage, gcc, ubuntu-24.04)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (coverage, gcc, ubuntu-24.04)
The operation was canceled.
Linux (clang, shared)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Linux (clang, shared)
The operation was canceled.
macOS (shared, xcode, macos-14)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
macOS (shared, xcode, macos-14)
The operation was canceled.
macOS (shared, xcode, macos-13)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
macOS (shared, xcode, macos-13)
The operation was canceled.
Windows (amalgamation, x86_64, windows-2022)
Canceling since a higher priority waiting request for 'ci @ tls/ml_kem' exists
Analysis (format, gcc, ubuntu-24.04)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
Analysis (format, gcc, ubuntu-24.04)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
Clang Tidy
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
Clang Tidy
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
Linux (gcc, static)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
Linux (gcc, static)
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.