Skip to content

[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]#4420

Merged
nvauto merged 1 commit intorelease/26.04from
bot-submodule-sync-release/26.04
Mar 31, 2026
Merged

[submodule-sync] bot-submodule-sync-release/26.04 to release/26.04 [skip ci] [bot]#4420
nvauto merged 1 commit intorelease/26.04from
bot-submodule-sync-release/26.04

Conversation

@nvauto
Copy link
Copy Markdown
Collaborator

@nvauto nvauto commented Mar 31, 2026

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: 5200ed6, cudf commit SHA: rapidsai/cudf@a042f21

This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 31, 2026

HEAD commit SHA: 5200ed6, CUDF commit SHA: rapidsai/cudf@a042f21
Test passed: True

@nvauto nvauto merged commit c7fbe9b into release/26.04 Mar 31, 2026
@nvauto
Copy link
Copy Markdown
Collaborator Author

nvauto commented Mar 31, 2026

SUCCESS - auto-merge

@nvauto nvauto deleted the bot-submodule-sync-release/26.04 branch March 31, 2026 05:21
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 31, 2026

Greptile Summary

This is a routine automated submodule sync PR that advances the thirdparty/cudf submodule pointer from commit fb3682f987341c37c7d89be43aec6a394c78fed0 to a042f2119703290d0ef58dd4e217a4fcfff62fdc, keeping the dependency aligned with the release/26.04 branch of rapidsai/cudf. The .gitmodules configuration correctly tracks the release/26.04 branch, and this matches multiple prior automated sync commits already merged into the same branch. There are no logic, syntax, or style issues to flag — the only change is the submodule commit reference.

Confidence Score: 5/5

Safe to merge — single-file submodule pointer update with no code changes, consistent with the established automated sync pattern.

The PR contains exactly one change: advancing the cudf submodule reference to the latest commit on the matching release/26.04 branch. No source files, build configs, or logic are modified. The .gitmodules branch tracking is correct and aligns with this repository's release branch. Several identical automated syncs have been successfully merged previously.

No files require special attention.

Important Files Changed

Filename Overview
thirdparty/cudf Submodule pointer updated from fb3682f to a042f21 on the release/26.04 branch of rapidsai/cudf — no code changes in this repository.

Sequence Diagram

sequenceDiagram
    participant Bot as nvauto Bot
    participant Repo as spark-rapids-jni (release/26.04)
    participant cudf as rapidsai/cudf (release/26.04)

    cudf->>cudf: New commit a042f21 lands on release/26.04
    Bot->>Repo: Detect cudf submodule is behind
    Bot->>Repo: Open PR updating thirdparty/cudf pointer
    Note over Repo: fb3682f → a042f21
    Repo->>Repo: CI runs tests against new cudf
    Repo->>Repo: Auto-merge on CI pass
Loading

Reviews (1): Last reviewed commit: "Update submodule cudf to a042f2119703290..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant