Skip to content

net, tests, stuntime: Add L2 bridge client migration stuntime scenario#4867

Merged
rnetser merged 3 commits into
RedHatQE:mainfrom
Anatw:stuntime_l2_bridge_first_scenario
May 28, 2026
Merged

net, tests, stuntime: Add L2 bridge client migration stuntime scenario#4867
rnetser merged 3 commits into
RedHatQE:mainfrom
Anatw:stuntime_l2_bridge_first_scenario

Conversation

@Anatw
Copy link
Copy Markdown
Contributor

@Anatw Anatw commented May 14, 2026

Short description:

Implement stuntime scenario over Linux bridge in which the client VM migrates off the server node.

More details:
What this PR does / why we need it:

Establish a performance baseline and enable regression detection for Linux bridge live migration connectivity gaps (stuntime), mirroring the existing OVN localnet coverage.

Which issue(s) this PR fixes:
Special notes for reviewer:
  • The first commit is dedicated to the extraction of the shared stuntime lib, and the consequent import changes needed in the localnet stuntime sub-package.
  • For now, the global stuntime threshold is set to a 5s placeholder. Once we finish automating the remaining scenarios and have the baseline data to calibrate our expectations, we’ll replace this with a more precise, data-driven value.
  • measure_stuntime() is also introduced in PR net, tests, stuntime: Add OVN localnet migration stuntime scenarios  #4833. Whichever merges first takes precedence — the other will rebase and remove the duplicate.
jira-ticket:

https://redhat.atlassian.net/browse/CNV-84398

Summary by CodeRabbit

  • Tests

    • Added end-to-end L2 bridge migration tests with reusable server/client VM fixtures, IPv4/IPv6 parametrization, and an active ping-based stuntime measurement; updated a migration test to use the new fixtures and disabled several variants pending validation.
  • Chores

    • Consolidated stuntime measurement into a shared helper used across test suites.
    • VM provisioning now supports optional template metadata labels and related import cleanup.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

Warning

Review limit reached

@Anatw, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 39 minutes and 12 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 9cc77352-354f-4b80-8a5f-07c77be19c01

📥 Commits

Reviewing files that changed from the base of the PR and between c91292c and 36eae7a.

📒 Files selected for processing (3)
  • tests/network/l2_bridge/libl2bridge.py
  • tests/network/l2_bridge/migration_stuntime/conftest.py
  • tests/network/l2_bridge/migration_stuntime/test_migration_stuntime.py
📝 Walkthrough

Walkthrough

Refactors stuntime measurement into a shared helper, adds labels support to the secondary VM builder, introduces L2-bridge NAD and server/client VM fixtures with ip-family support and an active-ping fixture, and updates localnet and L2-bridge tests to use the shared measurement API.

Changes

L2 Bridge Stuntime Migration Tests and Shared Library Refactoring

Layer / File(s) Summary
Shared stuntime library refactoring
tests/network/libs/stuntime.py
Generalizes module docstring, removes compute_stuntime, and adds measure_stuntime that stops an active ContinuousPing and computes stuntime via a private _compute_stuntime helper.
Localnet stuntime test updates
tests/network/localnet/migration_stuntime/conftest.py, tests/network/localnet/migration_stuntime/test_migration_stuntime.py
Switches localnet imports to shared tests.network.libs.stuntime and consolidates stuntime measurement into measure_stuntime(active_ping=...).
L2 bridge VM builder enhancement
tests/network/l2_bridge/libl2bridge.py
Adds Metadata import and an optional labels parameter to secondary_network_vm; merges provided labels into spec.template.metadata.labels.
L2 bridge stuntime test fixtures
tests/network/l2_bridge/migration_stuntime/conftest.py
Adds module-scoped l2-bridge-nad, class-scoped server and client VMs with randomized secondary IPv4/IPv6 addresses and server-label affinity, a class-scoped ip_family fixture, and function-scoped l2_bridge_active_ping yielding a ContinuousPing from client to server per IP family.
L2 bridge migration test updates
tests/network/l2_bridge/migration_stuntime/test_migration_stuntime.py
Adds pytest.mark.tier3, class-level ip_family parametrization, updates test_client_migrates_off_server_node to accept admin and stuntime fixtures and call measure_stuntime(active_ping=...), then assert threshold; disables remaining tests in the class.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested labels

new-tests

Suggested reviewers

  • nirdothan
  • orelmisan
  • EdDev
  • yossisegev
  • servolkov
  • frenzyfriday
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main change: adding an L2 bridge client migration stuntime scenario, is under 120 characters (70 chars), and directly relates to the changeset.
Description check ✅ Passed The PR description includes all required sections: short description, what/why, jira-ticket link, and special reviewer notes about threshold placeholders and duplicate handling.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stp Link Required ✅ Passed Newly added test file tests/network/l2_bridge/migration_stuntime/test_migration_stuntime.py contains module-level docstring with STP link URL, meeting the requirement.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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

coderabbitai[bot]
coderabbitai Bot previously approved these changes May 14, 2026
@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

Clean rebase detected — no code changes compared to previous head (efe097c).

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

  1. Examine code changes in each modified file
  2. Identify affected code paths, functions, and classes
  3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes
  4. Trace test dependencies through imports, shared utilities, and fixture inheritance
  5. Detect new tests introduced in the PR
  6. Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
    • Changes to files/functions used by tests marked with @pytest.mark.smoke
    • Changes to fixtures or utilities imported by smoke tests
    • Changes to conftest.py files that may affect smoke test execution
    • Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

Your deliverable:
Your change request comment will be based on the following requirements:

Test Execution Plan

  • Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
  • path/to/test_file.py - When the entire test file needs verification
  • path/to/test_file.py::TestClass::test_method - When specific test(s) needed
  • path/to/test_file.py::test_function - When specific test(s) needed
  • -m marker - When specific marker(s) can be used to cover multiple cases.

Guidelines:

  • Include only tests directly affected by the changes
  • Use a full file path only if ALL tests in that file require verification
  • Use file path + test name if only specific tests are needed
  • If a test marker can cover multiple files/tests, provide the marker
  • Balance coverage vs over-testing - Keep descriptions minimal

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

  • Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
  • Test Plan: MUST verify both WITH and WITHOUT hardware:
    • Run affected tests on cluster WITH hardware
    • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

  1. YOUR ONLY DELIVERABLE: Post an inline review comment containing the test execution plan on the first changed line
  2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
  3. FALLBACK ONLY: If submitting the review fails after retrying, post as a regular PR comment
  4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

  • ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
  • ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
  • ❌ Do NOT add any follow-up comments after submitting the review
  • ❌ Do NOT reply to confirm task completion
  • ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL: Before setting "Run smoke tests: True", you MUST use shell scripts to:
- Trace the actual fixture dependency chain from smoke tests to changed fixtures
- Verify that smoke tests actually import/use changed utilities or functions
- Confirm the dependency path exists; do NOT assume based on scope or semantics
- Be conservative: Session-scoped fixtures or infrastructure-sounding names do NOT
automatically mean smoke test impact. Only flag smoke test impact when you can
demonstrate a concrete dependency path.
WRONG: "This session-scoped storage fixture might affect smoke tests"
RIGHT: "Smoke test X uses fixture Y, which depends on the changed fixture Z"

Comment thread tests/network/l2_bridge/libl2bridge.py
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 27, 2026

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get latest commit SHA
gh pr view 4867 --json headRefOid --jq '.headRefOid'

# Get changed files
gh pr view 4867 --json files --jq '.files[].path'

# Get the diff to find the first changed line of the first file
gh pr diff 4867 -- tests/network/l2_bridge/libl2bridge.py | head -30

# Check smoke test files for any imports from changed modules
rg -n "smoke" tests/ --type py -l | head -20

Length of output: 1303


🏁 Script executed:

#!/bin/bash
# Get the diff for libl2bridge.py
gh pr diff 4867 | grep -A 40 "diff --git a/tests/network/l2_bridge/libl2bridge.py"

# Check smoke test files for imports from libl2bridge or stuntime
rg -n "libl2bridge\|stuntime" tests/virt/node/general/test_container_disk_vm.py tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py tests/storage/cdi_clone/test_clone.py tests/storage/cdi_import/test_import_registry.py tests/storage/cdi_upload/test_upload_virtctl.py tests/storage/cdi_import/test_import_http.py tests/install_upgrade_operators/csv/test_csv.py tests/infrastructure/instance_types/supported_os/test_rhel_os.py 2>/dev/null || echo "No matches found"

Length of output: 2839


🏁 Script executed:

#!/bin/bash
gh api \
  --method POST \
  /repos/RedHatQE/openshift-virtualization-tests/pulls/4867/reviews \
  --input - <<'EOF'
{
  "commit_id": "898daa4a6b4b26c261a6c36f97e501739a8a463f",
  "event": "COMMENT",
  "comments": [
    {
      "path": "tests/network/l2_bridge/libl2bridge.py",
      "line": 15,
      "body": "**Test Execution Plan**\n\n- **Run smoke tests: False** — Verified: no smoke test file imports `libl2bridge`, `stuntime`, or any other changed module.\n\n**Tests to run:**\n\n- `tests/network/l2_bridge/migration_stuntime/test_migration_stuntime.py` — New L2 bridge stuntime tests (IPv4 + IPv6 parametrized, `tier3`).\n- `tests/network/localnet/migration_stuntime/test_migration_stuntime.py::TestMigrationStuntime::test_client_migrates_off_server_node` — Refactored to use shared `measure_stuntime()`; verify behavior is unchanged."
    }
  ]
}
EOF

Length of output: 2656



@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

/retest all

Auto-triggered: Files in this PR were modified by merged PR #4833.

Overlapping files

tests/network/localnet/migration_stuntime/conftest.py
tests/network/localnet/migration_stuntime/test_migration_stuntime.py

Anatw added 2 commits May 27, 2026 16:19
Extract Stuntime measurement utilities to tests/network/libs/ to enable
reuse for l2_bridge stuntime tests and future network types.
Update localnet imports accordingly.

Signed-off-by: Anat Wax <awax@redhat.com>
Assisted-by: Claude <noreply@anthropic.com>
Move helpers below ContinuousPing class to eliminate the forward
reference.
Make compute_stuntime private (_compute_stuntime) since
it's only called from measure_stuntime. This clarifies the public
API surface: callers use measure_stuntime, not the internal helper.

Signed-off-by: Anat Wax <awax@redhat.com>
Assisted-by: Claude <noreply@anthropic.com>
@Anatw
Copy link
Copy Markdown
Contributor Author

Anatw commented May 27, 2026

Change: rebase on main (absorb localnet stuntime additions from #4833)

coderabbitai[bot]
coderabbitai Bot previously approved these changes May 27, 2026
Implement stuntime scenario over Linux bridge in which client VM
migrates off the server node. This scenario will serve as a baseline for
future performance testing, mirroring the existing OVN localnet stuntime
coverage.

Signed-off-by: Anat Wax <awax@redhat.com>
Assisted-by: Claude <noreply@anthropic.com>
@Anatw
Copy link
Copy Markdown
Contributor Author

Anatw commented May 27, 2026

Change: fix flake8 failure - rename ip_family for l2_bridge.

@Anatw
Copy link
Copy Markdown
Contributor Author

Anatw commented May 27, 2026

/build-and-push-container

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

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

@Anatw
Copy link
Copy Markdown
Contributor Author

Anatw commented May 27, 2026

/verified

Tested on bm03-tlv2
Openshift version: 4.22.0-rc.2
CNV version: 4.22.0
HCO image: brew.registry.redhat.io/rh-osbs/iib:1141649
openshift-virtualization-tests-runner/5375
PYTEST_PARAMS: -s -o log_cli=true -m tier3 --jira --cluster-sanity-skip-storage-check tests/network/l2_bridge/migration_stuntime/ tests/network/l2_bridge/test_l2_ovs_linux_bridge.py tests/network/localnet/migration_stuntime/test_migration_stuntime.py
==== 14 passed, 9 deselected, 99 warnings in 2570.70s (0:42:50) ====

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

  1. Examine code changes in each modified file
  2. Identify affected code paths, functions, and classes
  3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes
  4. Trace test dependencies through imports, shared utilities, and fixture inheritance
  5. Detect new tests introduced in the PR
  6. Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
    • Changes to files/functions used by tests marked with @pytest.mark.smoke
    • Changes to fixtures or utilities imported by smoke tests
    • Changes to conftest.py files that may affect smoke test execution
    • Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

Your deliverable:
Your change request comment will be based on the following requirements:

Test Execution Plan

  • Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
  • path/to/test_file.py - When the entire test file needs verification
  • path/to/test_file.py::TestClass::test_method - When specific test(s) needed
  • path/to/test_file.py::test_function - When specific test(s) needed
  • -m marker - When specific marker(s) can be used to cover multiple cases.

Guidelines:

  • Include only tests directly affected by the changes
  • Use a full file path only if ALL tests in that file require verification
  • Use file path + test name if only specific tests are needed
  • If a test marker can cover multiple files/tests, provide the marker
  • Balance coverage vs over-testing - Keep descriptions minimal

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

  • Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
  • Test Plan: MUST verify both WITH and WITHOUT hardware:
    • Run affected tests on cluster WITH hardware
    • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

  1. YOUR ONLY DELIVERABLE: Post an inline review comment containing the test execution plan on the first changed line
  2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
  3. FALLBACK ONLY: If submitting the review fails after retrying, post as a regular PR comment
  4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

  • ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
  • ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
  • ❌ Do NOT add any follow-up comments after submitting the review
  • ❌ Do NOT reply to confirm task completion
  • ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL: Before setting "Run smoke tests: True", you MUST use shell scripts to:
- Trace the actual fixture dependency chain from smoke tests to changed fixtures
- Verify that smoke tests actually import/use changed utilities or functions
- Confirm the dependency path exists; do NOT assume based on scope or semantics
- Be conservative: Session-scoped fixtures or infrastructure-sounding names do NOT
automatically mean smoke test impact. Only flag smoke test impact when you can
demonstrate a concrete dependency path.
WRONG: "This session-scoped storage fixture might affect smoke tests"
RIGHT: "Smoke test X uses fixture Y, which depends on the changed fixture Z"

Comment thread tests/network/l2_bridge/libl2bridge.py
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 27, 2026

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get latest commit SHA
gh pr view 4867 --json headRefOid --jq '.headRefOid'

# Get changed files
gh pr view 4867 --json files --jq '.files[].path'

# Get diff for libl2bridge.py to find first changed line
gh pr diff 4867 | grep -A 50 "diff --git a/tests/network/l2_bridge/libl2bridge.py"

# Check smoke test files for any imports from changed modules
rg -n "pytest.mark.smoke" tests/ --type py -l | head -20

Length of output: 3687


🏁 Script executed:

#!/bin/bash
# Verify smoke test files don't import from changed modules
rg -n "libl2bridge\|stuntime\|libs\.vm\.spec" \
  tests/virt/cluster/common_templates/rhel/test_rhel_os_support.py \
  tests/virt/node/general/test_container_disk_vm.py \
  tests/storage/cdi_import/test_import_http.py \
  tests/storage/cdi_upload/test_upload_virtctl.py \
  tests/storage/cdi_import/test_import_registry.py \
  tests/storage/cdi_clone/test_clone.py \
  tests/install_upgrade_operators/csv/test_csv.py \
  tests/infrastructure/instance_types/supported_os/test_rhel_os.py 2>/dev/null || echo "No matches found"

# Post inline comment on line 15 of libl2bridge.py (the Metadata import change)
gh api \
  --method POST \
  /repos/RedHatQE/openshift-virtualization-tests/pulls/4867/reviews \
  --input - <<'EOF'
{
  "commit_id": "36eae7a690783290d6d32be1e058bdbf5094348a",
  "event": "COMMENT",
  "comments": [
    {
      "path": "tests/network/l2_bridge/libl2bridge.py",
      "line": 15,
      "body": "**Test Execution Plan**\n\n- **Run smoke tests: False** — Verified: none of the 8 smoke-marked test files import `libl2bridge`, `stuntime`, or `libs.vm.spec` (confirmed via codebase search on latest commit).\n\n**Tests to run:**\n\n- `tests/network/l2_bridge/migration_stuntime/test_migration_stuntime.py` — New L2 bridge stuntime tests (IPv4 + IPv6 parametrized, `tier3`).\n- `tests/network/localnet/migration_stuntime/test_migration_stuntime.py::TestMigrationStuntime::test_client_migrates_off_server_node` — Refactored to use shared `measure_stuntime()`; verify behavior is unchanged."
    }
  ]
}
EOF

Length of output: 3448



@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

/retest all

Auto-triggered: Files in this PR were modified by merged PR #4962.

Overlapping files

tests/network/l2_bridge/libl2bridge.py

@Anatw
Copy link
Copy Markdown
Contributor Author

Anatw commented May 27, 2026

/retest build-container

@rnetser
Copy link
Copy Markdown
Collaborator

rnetser commented May 28, 2026

/approve
/lgtm

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

Successfully removed PR tag: quay.io/openshift-cnv/openshift-virtualization-tests:pr-4867.

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

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

@Anatw
Copy link
Copy Markdown
Contributor Author

Anatw commented May 28, 2026

/retest build-container

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