CherryPicked: [cnv-4.19] tests, net, l2_bridge: mark interface stability scenarios as t3#4955
Merged
rnetser merged 1 commit intoMay 26, 2026
Conversation
##### 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>
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 |
|
Report bugs in Issues Welcome! 🎉This pull request will be automatically processed with the following features: 🔄 Automatic Actions
📋 Available CommandsPR Status Management
Review & Approval
Testing & Validation
Container Operations
Cherry-pick Operations
Label Management
✅ Merge RequirementsThis PR will be automatically approved when the following conditions are met:
📊 Review ProcessApprovers and ReviewersApprovers:
Reviewers:
Available Labels
AI Features
💡 Tips
For more information, please refer to the project documentation or contact the maintainers. |
azhivovk
approved these changes
May 21, 2026
yossisegev
approved these changes
May 25, 2026
servolkov
approved these changes
May 26, 2026
Collaborator
|
/approve |
Contributor
|
New container for quay.io/openshift-cnv/openshift-virtualization-tests:cnv-4.19 published |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick from
mainbranch, original PR: #4619, PR owner: Anatw