[DO NOT MERGE] flaky error experiment - #11002
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
/ok to test 42b0693 |
This comment has been minimized.
This comment has been minimized.
|
/ok to test dba8569 |
This comment has been minimized.
This comment has been minimized.
|
/ok to test 83f58ac |
This comment has been minimized.
This comment has been minimized.
|
/ok to test 83f58ac |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
/ok to test fa5bf1b |
|
This CI job seems to show the issue with a decent traceback https://github.com/NVIDIA/cccl/actions/runs/33000505843/job/98289634645?pr=11002 |
This comment has been minimized.
This comment has been minimized.
|
/ok to test a61001e |
This comment has been minimized.
This comment has been minimized.
|
/ok to test b476ab1 |
🥳 CI Workflow Results🟩 Finished in 38m 20s: Pass: 100%/8 | Total: 4h 29m | Max: 36m 40sSee results here. AI failure analysis1. Temporary matrix override intentionally fails workflow verification · 1 jobExplanation: The PR leaves `workflows.override` populated with the temporary `nvjitlink_repro` matrix. The verification step deliberately rejects any non-empty override, so the workflow cannot pass until this diagnostic configuration is reset. Evidence: Verify and summarize workflow results, step 3 Root cause: `ci/matrix.yaml` intentionally contains a temporary diagnostic entry under `workflows.override`. The workflow verifier treats that state as an actionable configuration failure, independently of other failed jobs. Sources: ci/matrix.yaml:71. Suggested next steps: Remove the `nvjitlink_repro` entry while retaining the empty `override:` key, then rerun the repository's focused matrix-generation or workflow-verification check. Copy this prompt into a coding agentJobs: 2. cuGraph temporaries select RMM's deleted device_scalar constructor · 1 jobExplanation: cuGraph compilation fails at repeated `rmm::device_scalar<size_t>` initializations that pass temporary values such as `size_t{0}`. The checked-out RMM header deletes the matching rvalue overload, preventing cuGraph and the RAPIDS compatibility job from building. Evidence: Build RAPIDS (optional) / rmm ucxx raft cuvs cugraph wholegraph, step 6 Root cause: The RAPIDS job checks out both RMM and cuGraph from their current `main` branches, but the saved versions are API-incompatible: RMM rejects temporary-backed scalar construction while cuGraph still uses it. The logs do not record the cloned repositories' commit SHAs, so the exact upstream revision introducing the mismatch cannot be identified from the collected evidence. Suggested next steps: Update the cuGraph call sites to pass an lvalue with sufficient lifetime or use RMM's supported initialization API; otherwise temporarily pin compatible RMM and cuGraph revisions. Reproduce with `RAPIDS_LIBS='rmm ucxx raft cuvs cugraph wholegraph' .devcontainer/launch.sh -d -c 13.3 -H rapids-conda -- ./ci/rapids/rapids-entrypoint.sh /bin/bash -li -c 'uninstall-all -j -qqq && clean-all -j && build-all -j0 -v || exec /bin/bash -li'`. Copy this prompt into a coding agentJobs: |
Test to try to figure out why CI is being flaky