[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]#4417
Conversation
Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
|
HEAD commit SHA: f2b6c79, CUDF commit SHA: rapidsai/cudf@fb3682f |
|
SUCCESS - auto-merge |
Greptile SummaryThis is a routine automated submodule sync PR created by the
Confidence Score: 5/5This PR is safe to merge — it is a single-line submodule pointer update with no source code changes. The entire diff is a one-line submodule hash bump on an automated bot PR that follows the exact same pattern as dozens of previously merged PRs on this branch. There are no logic, security, or data-integrity concerns to evaluate. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant Bot as nvauto Bot
participant SparkRapidsJNI as spark-rapids-jni (release/26.04)
participant CuDF as rapidsai/cudf (release/26.04)
CuDF->>CuDF: New commit landed (fb3682f)
Bot->>CuDF: Detect new HEAD on release/26.04
Bot->>SparkRapidsJNI: Open submodule-sync PR
Note over SparkRapidsJNI: thirdparty/cudf pointer<br/>9064d9d → fb3682f
SparkRapidsJNI->>SparkRapidsJNI: Run CI tests
SparkRapidsJNI->>SparkRapidsJNI: Auto-merge if tests pass
Reviews (1): Last reviewed commit: "Update submodule cudf to fb3682f987341c3..." | Re-trigger Greptile |
submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: f2b6c79, cudf commit SHA: rapidsai/cudf@fb3682f
This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.