Skip to content

feat(test): add runs: sub-runs support to pytest_runner - #8081

Open
archana-ramalingam wants to merge 6 commits into
mainfrom
users/aramalin/pytest-runner-subruns
Open

archana-ramalingam wants to merge 6 commits into
mainfrom
users/aramalin/pytest-runner-subruns

Conversation

@archana-ramalingam

@archana-ramalingam archana-ramalingam commented Sep 8, 2026 •

Copy link
Copy Markdown
Contributor

JIRA ID : N/A

Motivation

  • pytest_runner.py runs one pytest invocation per test category.
  • Sub-runs let a category to run suites that can't share one invocation (different paths, -m expressions, or client args).

Technical Details

  • A category may declare runs:, a list of sub-runs. Each runs as an independent pytest invocation with its own test_paths, markers, pytest_args, parallel_workers and JUnit file ({component}_{name}.xml); all share the category timeout and environment.
  • Run-all, not fail-fast: every sub-run reports; the step fails if any sub-run failed.
  • Sub-run names must be present and unique (they key the JUnit file).
  • An empty or non-list runs: fails instead of running nothing.
  • Categories without runs: take the existing single-run path.
  • No current consumer

Test Plan

  • pre-commit run --all-files

Test Result

  • N/A

Risk level

Low — additive CI test-runner capability; all existing (single-run) categories take existing code path.

@therock-pr-bot

therock-pr-bot Bot commented Sep 8, 2026 •

Copy link
Copy Markdown

❌ PR Check — Action Required

Check Status Details
📝 PR Description ❌ Fail Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword.
Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples:
• JIRA ID : TESTAUTO-6039
• JIRA ID - #330
• JIRA ID #330
• JIRA ID (on separate line)
ROCM-25757
• ISSUE ID : TESTUTO-3334
• ISSUE ID #3334
• ISSUE ID - TESTAUTO-3433
• ISSUE ID (on separate line)
AIRUNTIME-2352
• ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234
• Closes #10
• Fixes octo-org/octo-repo#100
• Resolves: #123
• #123
• https://github.com/<org_name>/<repo_name>/issues/123
Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files ✅ Pass —
🧪 Unit Test ✅ Pass —
🔎 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

  • ❌ PR Description

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.

🙋 Wish to Override Policy?

@therock-pr-bot

therock-pr-bot Bot commented Sep 8, 2026 •

Copy link
Copy Markdown

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

  • ❌ PR Description

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

@geomin12 geomin12 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.

title is unclear and changes seen here are unrelated to tensilelite. some code changes are also irrelevant and out of scope

we are using mi455 in coordination with leadership + mi455 war room team. we can close this PR out

@archana-ramalingam archana-ramalingam changed the title test(tensilelite): Enable on-demand gfx1250 public CI feat(ci): Enable on-demand gfx1250 public CI Sep 9, 2026
@archana-ramalingam archana-ramalingam changed the title feat(ci): Enable on-demand gfx1250 public CI feat(test): add runs: sub-runs support to pytest_runner Sep 10, 2026
@archana-ramalingam
archana-ramalingam requested review from dileepr1 and geomin12 and removed request for rahulc-gh September 10, 2026 01:36
@therock-pr-bot therock-pr-bot Bot added the Not ready to Review PR has unresolved policy failures — reviews blocked label Oct 8, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Not ready to Review PR has unresolved policy failures — reviews blocked

Projects

Status: TODO

Development

Successfully merging this pull request may close these issues.

2 participants