Skip to content

CherryPicked: [cnv-4.19] tests, net, l2_bridge: mark interface stability scenarios as t3#4955

Merged
rnetser merged 1 commit into
cnv-4.19from
CherryPicked-mark_interface_stability_as_tier3-4UN3D
May 26, 2026
Merged

CherryPicked: [cnv-4.19] tests, net, l2_bridge: mark interface stability scenarios as t3#4955
rnetser merged 1 commit into
cnv-4.19from
CherryPicked-mark_interface_stability_as_tier3-4UN3D

Conversation

@cnv-tests-github-webhook-dollierp

Copy link
Copy Markdown

Cherry-pick from main branch, original PR: #4619, PR owner: Anatw

##### Short description:
Relocate Interface Stability scenarios from Tier 2 to Tier 3 to optimize
CI pipeline performance.

##### What this PR does / why we need it:
This PR migrates the Interface Stability test suite to the Tier 3 lane
to optimize our CI resource allocation. These scenarios require a
five-minute monitoring period per test, totaling approximately 15
minutes of execution time. By moving these tests from Tier 2, which runs
three times a week, to the weekly Tier 3 cadence, we significantly
reduce the execution load on our mid-week lanes. This adjustment ensures
that Tier 2 remains lean and focused on providing faster feedback loops
for frequent integration checks while still maintaining essential
long-term stability coverage on a weekly basis.

##### Which issue(s) this PR fixes:

##### Special notes for reviewer:
The test logic remains identical; only the execution tier/metadata has
been updated to reflect the new weekly cadence. This change aligns with
our goal to prioritize Tier 2 for faster, high-frequency signals.

##### jira-ticket:

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Tests**
* Marked all tests in the interface stability test module as tier3,
ensuring uniform classification across contained tests (including those
with other markers). This improves test organization, filtering, and
execution categorization for stability-related test runs.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: ‪Anat Wax <awax@redhat.com>
@Anatw

Anatw commented May 20, 2026

Copy link
Copy Markdown
Contributor

/verified

uv run pytest -s -o log_cli=true -m tier3 --jira --collect-only tests/network/l2_bridge/vmi_interfaces_stability/test_interfaces_stability.py
...

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

  • Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
  • Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
  • Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
  • Branch Labeling: Branch-specific labels are applied to track the target branch
  • Auto-verification: Auto-verified users have their PRs automatically marked as verified
  • Labels: Enabled categories: branch, can-be-merged, cherry-pick, has-conflicts, hold, needs-rebase, size, verified, wip

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (approvers only)
  • /hold cancel - Unblock PR merging
  • /verified - Mark PR as verified
  • /verified cancel - Remove verification status
  • /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
  • /regenerate-welcome - Regenerate this welcome message

Review & Approval

  • /lgtm - Approve changes (looks good to me)
  • /approve - Approve PR (approvers only)
  • /assign-reviewers - Assign reviewers based on OWNERS file
  • /assign-reviewer @username - Assign specific reviewer
  • /check-can-merge - Check if PR meets merge requirements

Testing & Validation

  • /retest tox - Run Python test suite with tox
  • /retest build-container - Rebuild and test container image
  • /retest verify-bugs-are-open - verify-bugs-are-open
  • /retest all - Run all available tests

Container Operations

  • /build-and-push-container - Build and push container image (tagged with PR number)
    • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

  • /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
    • Multiple branches: /cherry-pick branch1 branch2 branch3

Label Management

  • /<label-name> - Add a label to the PR
  • /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

  1. Approval: /approve from at least one approver
  2. LGTM Count: Minimum 2 /lgtm from reviewers
  3. Status Checks: All required status checks must pass
  4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
  5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

  • EdDev

Reviewers:

  • Anatw
  • EdDev
  • azhivovk
  • frenzyfriday
  • nirdothan
  • orelmisan
  • servolkov
  • yossisegev
Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve
AI Features
  • Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6[1m])

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
  • Cherry-picking: Cherry-pick labels are processed when the PR is merged
  • Container Builds: Container images are automatically tagged with the PR number
  • Permission Levels: Some commands require approver permissions
  • Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

@rnetser

rnetser commented May 26, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@rnetser rnetser merged commit 5b0300e into cnv-4.19 May 26, 2026
23 checks passed
@rnetser rnetser deleted the CherryPicked-mark_interface_stability_as_tier3-4UN3D branch May 26, 2026 10:40
@openshift-virtualization-qe-bot-2

Copy link
Copy Markdown
Contributor

New container for quay.io/openshift-cnv/openshift-virtualization-tests:cnv-4.19 published

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.

9 participants