Skip to content
build

Use strict priority in CI conda tests (#1583) #2

Sign in to view logs

Use strict priority in CI conda tests (#1583)

Use strict priority in CI conda tests (#1583) #2

Triggered via push November 24, 2025 05:47
@LizYouLizYou
pushed 2cf5fa7
main
Status Startup failure
Total duration –
Artifacts –

build.yaml

on: push
cpp-build  /  compute-matrix
cpp-build / compute-matrix
wheel-build-libcuvs  /  compute-matrix
wheel-build-libcuvs / compute-matrix
Matrix: rocky8-clib-standalone-build
Waiting for pending jobs
Matrix: cpp-build / build
Waiting for pending jobs
Matrix: wheel-build-libcuvs / build
Waiting for pending jobs
Matrix: rust-build
Waiting for pending jobs
python-build  /  compute-matrix
python-build / compute-matrix
Matrix: go-build
Waiting for pending jobs
Matrix: java-build
Waiting for pending jobs
wheel-build-cuvs  /  compute-matrix
wheel-build-cuvs / compute-matrix
wheel-publish-libcuvs  /  wheels publish
wheel-publish-libcuvs / wheels publish
Matrix: python-build / build
Waiting for pending jobs
Matrix: wheel-build-cuvs / build
Waiting for pending jobs
upload-conda  /  upload
upload-conda / upload
docs-build  /  build
docs-build / build
wheel-publish-cuvs  /  wheels publish
wheel-publish-cuvs / wheels publish
Matrix: rust-publish / rust-publish
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

1 error
Invalid workflow file: .github/workflows/build.yaml#L35
The workflow is not valid. .github/workflows/build.yaml (Line: 35, Col: 3): Error calling workflow 'rapidsai/shared-workflows/.github/workflows/conda-cpp-build.yaml@main'. The workflow is requesting 'id-token: write', but is only allowed 'id-token: none'.