Skip to content

test(miopen)[ALMIOPEN-2867]: add find/optimizer/misc gtest families to test_categories.yaml (1/9) - #13403

Closed
aalabsi-amd wants to merge 1 commit into
developfrom
users/aalabsi-amd/miopen-test-categories-jenkins-parity-01-find-optimizers-misc
Closed

aalabsi-amd wants to merge 1 commit into
developfrom
users/aalabsi-amd/miopen-test-categories-jenkins-parity-01-find-optimizers-misc

Conversation

@aalabsi-amd

@aalabsi-amd aalabsi-amd commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

JIRA ID : ALMIOPEN-2867 Chunk 1/9: find/allocator/misc suites, Adam/AmpAdam, pure unprefixed suites.

Motivation

Chunk 1/9 of jenkins tests parity: find/allocator/misc suites, Adam/AmpAdam, pure unprefixed suites.

Technical Details

Jenkins runs these via its FP32/FP16/... filter; no pattern selected them. Placement follows measured per-test time (Jenkins old run and TheRock gfx942 logs, median ms): Smoke/unprefixed cases also run in standard; Full/ cases run in comprehensive/full only.

Newly selected: 1094 cases (1094 that Jenkins runs, 0 beyond Jenkins). Added per tier (cases, est. serial time; divide by 4 shards for per-shard):
standard +74 cases, +0.6 min
comprehensive +1094 cases, +1.3 min
full +1094 cases, +1.3 min

  • Full/ cases are excluded from standard (it is already at its time budget).

Checked against the TheRock 2026-09-22 miopen_gtest (real --gtest_filter): nothing removed in any tier or arch variant, quick/ffm-quick unchanged, and the added cases equal an independently derived expectation.
Part of a 9-way split of one change; chunks touch disjoint cases and may merge in any order, one at a time (they edit the same YAML anchors, so rebase between merges).

Test Plan

Test it with three cats standard, comprehensive and full and make sure tests pass fully and time added is reasonable and within budget.

Test Result

Submission Checklist

…es.yaml (1/9)

Chunk 1/9: find/allocator/misc suites, Adam/AmpAdam, pure unprefixed suites.

Jenkins runs these via its *FP32*/*FP16*/... filter; no pattern selected
them. Placement follows measured per-test time (Jenkins build #1034 and
TheRock gfx942 logs, median ms): Smoke/unprefixed cases also run in
standard; Full/ cases run in comprehensive/full only.

Newly selected: 1094 cases (1094 that Jenkins runs, 0 beyond Jenkins).
Added per tier (cases, est. serial time; divide by 4 shards for per-shard):
  standard      +74 cases, +0.6 min
  comprehensive +1094 cases, +1.3 min
  full          +1094 cases, +1.3 min
- Full/ cases are excluded from standard (it is already at its time budget).

Checked against the TheRock 2026-09-22 miopen_gtest (real --gtest_filter): nothing removed in
any tier or arch variant, quick/ffm-quick unchanged, and the added cases equal an
independently derived expectation.
Part of a 9-way split of one change; chunks touch disjoint cases and may merge in any
order, one at a time (they edit the same YAML anchors, so rebase between merges).
@therock-pr-bot

therock-pr-bot Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

⏳ Waiting on Required Checks

⏳ Required checks have not all concluded yet. This bot run is exiting without failing so those checks can report independently.

Check Status Details
📝 PR Description ✅ Pass —
⛔ Forbidden Files ✅ Pass —
🧪 Unit Test ✅ Pass PR does not contain code files — Unit Test auto-passed
🔎 pre-commit ⏳ Pending ⏳ Still running…
🚫 Draft PR 🔜 To Be Enabled —
🚩 Feature Flag 🔜 To Be Enabled —
📊 Code Coverage 🔜 To Be Enabled —

⏳ Required checks are still running or have not started yet.
This PR is not ready for review until they complete.

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

🙋 Wish to Override Policy?

@therock-pr-bot

therock-pr-bot Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

⏳ Waiting for required checks to start or finish:

  • ⏳ pre-commit

@aalabsi-amd aalabsi-amd changed the title test(miopen): add find/optimizer/misc gtest families to test_categories.yaml (1/9) test(miopen)[ALMIOPEN-2867]: add find/optimizer/misc gtest families to test_categories.yaml (1/9) Oct 9, 2026
@aalabsi-amd
aalabsi-amd marked this pull request as ready for review October 10, 2026 01:52
@aalabsi-amd
aalabsi-amd requested a review from a team as a code owner October 10, 2026 01:52

@JonathanLichtnerAMD JonathanLichtnerAMD 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. One minor comment

@@ -64,10 +64,26 @@ positive_patterns: &positive_patterns
- "*/GPU_Dropout*"
- "*/GPU_MIOpenDriver*"
- "*/GPU_HipGraphExist*"
# Jenkins-parity: Smoke/ and unprefixed cases also run in standard; Full/ cases run in comprehensive/full only.
# Chunk: find/allocator/misc suites, Adam/AmpAdam, pure unprefixed suites.

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.

This comment seems to imply that all the Full/* tests that were just added only run in comprehensive/full, but that is only true for a subset of these. Are these primarily Smoke/* tests? If so, we could add that explicitly here (or add one generic Smoke/* line, maybe immediately before Standard/*, below)

Maybe moving to Smoke/, Standard/, Full/* could help clean this up, so I am okay if you want to defer this

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.

One more note: you mention testing on standard, comprehensive and full in the TestPlan. Can we make this a checkbox list and also add doing sweeps on other architectures, such as gfx90a, navi, etc, or we might get surprised by nightly failures. The rock tests some architectures that our Jenkins CI didn't cover, and we have different timeout constraints for the rock's GHA vs Jenkins. Thanks!

@aalabsi-amd

Copy link
Copy Markdown
Contributor Author

Closing as this will be part of the full PR #13107

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.

2 participants