Quarantine: [IUO] xfail test_enable_fg_hco due to feature graduation #31771
Workflow file for this run
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
| # description: Add comment for CodeRabbit to add tests instructions. A change-request comment will be added to the PR. | |
| name: Request CodeRabbit tests instructions | |
| on: | |
| pull_request_target: | |
| types: [labeled] | |
| permissions: | |
| pull-requests: write | |
| contents: read | |
| jobs: | |
| comment-on-commit: | |
| if: | | |
| github.event.label.name == 'verified' && | |
| !contains(github.event.pull_request.user.login, 'renovate') | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Check team membership | |
| id: check-user-team | |
| uses: tspascoal/get-user-teams-membership@v3 | |
| with: | |
| team: cnvqe-bot | |
| username: ${{ github.event.pull_request.user.login }} | |
| GITHUB_TOKEN: ${{ secrets.BOT3_TOKEN }} | |
| - name: Create or update comment | |
| if: steps.check-user-team.outputs.is-member != 'true' | |
| uses: peter-evans/create-or-update-comment@v5 | |
| with: | |
| issue-number: ${{ github.event.pull_request.number }} | |
| token: ${{ secrets.BOT3_TOKEN }} | |
| body: | | |
| @coderabbitai | |
| <details> | |
| <summary>Test execution plan request details</summary> | |
| 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" | |
| </details> |