Skip to content

test: [rocWMMA] fix: Catch launch errors in regression test#8862

Merged
dysu-amd merged 1 commit into
developfrom
users/bsyrowik/rocwmma_catch_launch_errors
Jul 7, 2026
Merged

test: [rocWMMA] fix: Catch launch errors in regression test#8862
dysu-amd merged 1 commit into
developfrom
users/bsyrowik/rocwmma_catch_launch_errors

Conversation

@bsyrowik

@bsyrowik bsyrowik commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Motivation

If the device code we've loaded is for an invalid device we will never detect that, and will silently continue to compare invalid values without running the kernel.

Should make error signature for
JIRA ID: ROCM-27254
more clear.

Technical Details

This change catches that situation and will error out with a useful message instead of showing that the values we have are invalid.

Test Plan

Manual test.
CI flow.

Test Result

Submission Checklist

@bsyrowik bsyrowik requested a review from a team as a code owner June 26, 2026 19:44
@bsyrowik bsyrowik changed the title Catch launch errors [rocWMMA] Catch launch errors in regression test Jun 26, 2026
@therock-pr-bot

therock-pr-bot Bot commented Jun 26, 2026

Copy link
Copy Markdown

❌ PR Check — Action Required

Check Status Details
🌿 Branch Name ✅ Pass
📝 PR Title/Description ✅ Pass
Forbidden Files ✅ Pass
🧪 Unit Test ❌ Fail Error: Source/code files changed without an accompanying unit test.
Expected: add at least one test file named like test_<name>.py / test_<name>.cpp (or <name>_test.*).
Current: code file(s) changed: projects/rocwmma/test/regression/issue_example.cpp; no test file found
🔎 pre-commit ✅ Pass
🚫 Draft PR 🔜 To Be Enabled
🚩 Feature Flag 🔜 To Be Enabled
📊 Code Coverage 🔜 To Be Enabled

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

  • ❌ Unit Test

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

@therock-pr-bot

therock-pr-bot Bot commented Jun 26, 2026

Copy link
Copy Markdown

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

  • ❌ Unit Test

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.

@bsyrowik bsyrowik changed the title [rocWMMA] Catch launch errors in regression test [rocWMMA] fix: Catch launch errors in regression test Jun 26, 2026

@evedovelli evedovelli left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bsyrowik bsyrowik changed the title [rocWMMA] fix: Catch launch errors in regression test test: [rocWMMA] fix: Catch launch errors in regression test Jul 3, 2026
@dysu-amd

dysu-amd commented Jul 7, 2026

Copy link
Copy Markdown

Overriding, Math CI test hang looks unrelated to this and is a known issue to component team.

@dysu-amd dysu-amd merged commit 404d1bc into develop Jul 7, 2026
34 of 51 checks passed
@dysu-amd dysu-amd deleted the users/bsyrowik/rocwmma_catch_launch_errors branch July 7, 2026 16:49
assistant-librarian Bot pushed a commit to ROCm/rocWMMA that referenced this pull request Jul 7, 2026
test: [rocWMMA] fix: Catch launch errors in regression test
 (#8862)

## Motivation

If the device code we've loaded is for an invalid device we will never
detect that, and will silently continue to compare invalid values
without running the kernel.

Should make error signature for
JIRA ID: ROCM-27254
more clear.

## Technical Details

This change catches that situation and will error out with a useful
message instead of showing that the values we have are invalid.

## Test Plan

Manual test.
CI flow.

## Test Result

<!-- Briefly summarize test outcomes. -->

## Submission Checklist

- [x] Look over the contributing guidelines at
https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants