Skip to content

[workflows] Add support for extended tests via a label#101

Draft
lumachad wants to merge 2 commits intoamd-stagingfrom
users/lumachad/amd-staging/extended-testing
Draft

[workflows] Add support for extended tests via a label#101
lumachad wants to merge 2 commits intoamd-stagingfrom
users/lumachad/amd-staging/extended-testing

Conversation

@lumachad
Copy link
Copy Markdown
Collaborator

Add configurable test options to therock-test-packages workflow

Make the test workflow a reusable template by adding test_options.

This allows running tests with different configurations (e.g., --parallel,
--optimization, --check-type) without creating separate workflow files.

Add extended testing support with testing:extended label

Add support for triggering extended test suite when testing:extended label
is added to a PR. Five additional test jobs run serially after the standard
build, each with different test options: --parallel, --optimization=-O3,
--check-type check-read1, --check-type check-readmore, and a HIP board test
with --runtestflags=--target_board=hip --tests gdb.base/break.exp.

Extended test jobs use if: success() || failure() to ensure all tests run
even if one fails, while still showing which tests failed in the UI. This
provides complete test coverage on demand without slowing down the standard
CI pipeline.

@lumachad lumachad self-assigned this Apr 24, 2026
@lumachad lumachad added the testing:extended Triggers a run of extended tests for rocgdb label Apr 24, 2026
@lumachad lumachad force-pushed the users/lumachad/amd-staging/extended-testing branch 2 times, most recently from 53b9c06 to 9de4799 Compare April 27, 2026 14:47
lumachad and others added 2 commits April 28, 2026 06:22
Make the test workflow a reusable template by adding test_options.

This allows running tests with different configurations (e.g., --parallel,
--optimization, --check-type) without creating separate workflow files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add support for triggering extended test suite when testing:extended label
is added to a PR. Five additional test jobs run serially after the standard
build, each with different test options: --parallel, --optimization=-O3,
--check-type check-read1, --check-type check-readmore, and a HIP board test
with --runtestflags=--target_board=hip --tests gdb.base/break.exp.

Extended test jobs use `if: success() || failure()` to ensure all tests run
even if one fails, while still showing which tests failed in the UI. This
provides complete test coverage on demand without slowing down the standard
CI pipeline.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@lumachad lumachad force-pushed the users/lumachad/amd-staging/extended-testing branch from 9de4799 to 40ce9e5 Compare April 28, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing:extended Triggers a run of extended tests for rocgdb

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant