Skip to content

Remove need to register specific callback type, rather have specific … #11523

Remove need to register specific callback type, rather have specific …

Remove need to register specific callback type, rather have specific … #11523

Triggered via push October 29, 2025 20:37
Status Cancelled
Total duration 19m 2s
Artifacts 3

test.yml

on: push
build and test using cross - on centos7
4m 6s
build and test using cross - on centos7
Matrix: ffi
Matrix: ffi_bake
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 8 warnings
build and test using cross - on centos7
Canceling since a higher priority waiting request for ci-refs/heads/gyuheon0h/prof-12432-runtime-stacks-cross-centos7 exists
build and test using cross - on centos7
The operation was canceled.
FFI alpine-build via docker bake
Canceling since a higher priority waiting request for ci-refs/heads/gyuheon0h/prof-12432-runtime-stacks-alpine-build exists
FFI alpine-build via docker bake
The operation was canceled.
cargo test --workspace #ubuntu-latest
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
cargo test --workspace #windows-latest
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
cargo test --workspace #windows-latest
Process completed with exit code 101.
cargo test --workspace #macos-13
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
cargo test --workspace #ubuntu-latest ${RUST_VERSION}
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
cargo test --workspace #ubuntu-latest
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
cargo test --workspace #ubuntu-latest
cargo-nextest@0.9.96 for 'x86_64_linux' is not supported; fallback to cargo-binstall
cargo test --workspace #windows-latest
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
cargo test --workspace #windows-latest
cargo-nextest@0.9.96 for 'x86_64_windows' is not supported; fallback to cargo-binstall
cargo test --workspace #macos-13
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
cargo test --workspace #macos-13
cargo-nextest@0.9.96 for 'x86_64_macos' is not supported; fallback to cargo-binstall
cargo test --workspace #ubuntu-latest ${RUST_VERSION}
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
cargo test --workspace #ubuntu-latest ${RUST_VERSION}
cargo-nextest@0.9.96 for 'x86_64_linux' is not supported; fallback to cargo-binstall

Artifacts

Produced during runtime
Name Size Digest
libdatadog.macos-13 Expired
21 MB
sha256:0c928bd8d95807e14067eedeca47dbb00440532a3576cf60300d905fb5356cb3
libdatadog.ubuntu-latest Expired
26 MB
sha256:249e37e7a4f79dce668ce5ef04cfcfb8384c2f0f02b0bbcd60de08f8569b282b
libdatadog.windows-latest Expired
16.6 MB
sha256:32afe90d4d618f4c02078a6807a0184b42b959a0e253de5105a01ca20a4f6bd9