Bump rocm-systems from 093b66c to 077d0d5#3956
Conversation
|
TheRock CI checks not showing on the main screen here... |
geomin12
left a comment
There was a problem hiding this comment.
windows failed https://github.com/ROCm/TheRock/actions/runs/23046433626/job/66936677181?pr=3956 due to out of resources. will require a retry.
aside from that, tests seem good though
Bumps [rocm-systems](https://github.com/ROCm/rocm-systems) from `093b66c` to `077d0d5`. - [Release notes](https://github.com/ROCm/rocm-systems/releases) - [Commits](ROCm/rocm-systems@093b66c...077d0d5) --- updated-dependencies: - dependency-name: rocm-systems dependency-version: 077d0d5b7b0e7fb9f75c5e22a4cb9ac50df0bb18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
524f75d to
e0b6004
Compare
CI Triage - Patch Conflict (Code Failure)All 8 checks failed (re-triggered 3x, same failure). Root cause: patch conflict in Fetch sources for all Build jobs; CI Summary failed as cascade.
Root Cause: The patch 0003-Use-is_versioned-true-consistently-in-both-Comgr-Loa.patch cannot apply because the target line has shifted (patch expects line 777; 077d0d5 has it at line 811). On rocm-systems master the code has since changed to Action Required:
|
|
Superseded by #3984. |
|
Docs for how to work with patch files: https://github.com/ROCm/TheRock/tree/main/patches#resolving-conflicts-with-patches |
Bumps rocm-systems from
093b66cto077d0d5.Commits
077d0d5Add WSL ABI compatibility check for DXG thunk (#3985)67bec9aAIRUNTIME-1893 - Fix __smid for GFX12 (RDNA4) architecture (#3841)0c35076[AMD-SMI] Fix CI failure from stale repo in AlmaLinux8 Docker image (#4015)0d38731Update TheRock reference (rocm-systems) - 2026-03-10 (#3930)3bfbadfROCM-3970 - release mem object outside the critical region (#3913)439fb1crocr: Replace repeated 'kAqlProfileLib' probes for each GPUfb08634Fix KFDTest SDMAFillDataPacket to support GFX12 (#3969)384af90Update TheRock SHA in therock-rccl-ci-linux.yml to include rocprofiler MPI de...c3796ce[hip-tests] Introduce new mechanism for tagging and disabling tests - Part 5 ...1ce7ea2[rocshmem] CI: Disable RO flood testing, tracking issue AIROCSHMEM-324 (#3961)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)