Skip to content

[amd-staging-rocgdb-16] gdb: Skip rocm watchpoint tests in case not all GPUs are supported#115

Open
motokultivator wants to merge 1 commit intoamd-staging-rocgdb-16from
users/arikalo/two-gpus-watchpoint-crash
Open

[amd-staging-rocgdb-16] gdb: Skip rocm watchpoint tests in case not all GPUs are supported#115
motokultivator wants to merge 1 commit intoamd-staging-rocgdb-16from
users/arikalo/two-gpus-watchpoint-crash

Conversation

@motokultivator
Copy link
Copy Markdown
Contributor

In the case where there are multiple GPUs on the system, and some of them are not supported, rocgdb issues a warning about this during the "run" command. This change introduces recognition of this warning and skips tests that would fail in such cases.

A new procedure has been introduced, in rocm.exp, for this purpose, which can be extended to recognize other specific warnings.

The tests affected by this are:

gdb.rocm/aspace-watchpoint.exp
gdb.rocm/watchpoint-at-end-of-shader.exp
gdb.rocm/precise-memory-warning-watchpoint.exp

In the case where there are multiple GPUs on the system, and
some of them are not supported, rocgdb issues a warning about
this during the "run" command. This change introduces recognition
of this warning and skips tests that would fail in such cases.

A new procedure has been introduced, in rocm.exp, for this purpose,
which can be extended to recognize other specific warnings.

The tests affected by this are:

gdb.rocm/aspace-watchpoint.exp
gdb.rocm/watchpoint-at-end-of-shader.exp
gdb.rocm/precise-memory-warning-watchpoint.exp
@motokultivator motokultivator requested a review from a team as a code owner May 7, 2026 13:00
@github-actions github-actions Bot changed the title gdb: Skip rocm watchpoint tests in case not all GPUs are supported [amd-staging-rocgdb-16] gdb: Skip rocm watchpoint tests in case not all GPUs are supported May 7, 2026
@lumachad
Copy link
Copy Markdown
Collaborator

lumachad commented May 7, 2026

Please target amd-staging. amd-staging-rocgdb-16 is only supposed to get cherry-picks.

@simark
Copy link
Copy Markdown
Contributor

simark commented May 7, 2026

Also, if there are changes that would apply to upstream, would you like to send them upstream? I don't mind doing it but if you want to do it by yourself it's fine to, just let me know.

Copy link
Copy Markdown
Collaborator

@lumachad lumachad left a comment

Choose a reason for hiding this comment

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

Wrong branch.

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.

3 participants