Skip to content

[cnv-4.19] Add marker for class/module scoped data collection (#4118)#4293

Open
dshchedr wants to merge 1 commit intoRedHatQE:cnv-4.19from
dshchedr:add-marker-class-module-scoped-data-collection-cnv-4.19
Open

[cnv-4.19] Add marker for class/module scoped data collection (#4118)#4293
dshchedr wants to merge 1 commit intoRedHatQE:cnv-4.19from
dshchedr:add-marker-class-module-scoped-data-collection-cnv-4.19

Conversation

@dshchedr
Copy link
Copy Markdown
Collaborator

manual cherry-pick, original PR: #4118

…QE#4118)

Add marker for class/module scoped data collection

Add 5-minute buffer to prevent data gaps in must-gather.

Introduces a new @pytest.mark.data_collector_scope("module") marker
that enables module-level data collection timing. When applied to a
test file, all must-gather/log collection will use the timestamp from
the first test in the module instead of individual test timestamps.

Add a 5-minute buffer because must-gather runs multiple `oc adm inspect`
commands with the same `--since`, while 1.5-2 minutes may pass between
them.

Changes:
- Add data_collector_scope marker to pytest.ini
- Add Database.insert_module_start_time() to track first test in
  module
- Add Database.get_module_start_time() to retrieve module start time
- Update pytest_runtest_setup to check for marker and store module
  time
- Update pytest_exception_interact to use module time when marker
  present
- Add comprehensive unit tests for new database methods

Example: test_machinetype.py has class-scoped vm_for_machine_type_test
fixture. With the marker, if test_machine_type_after_vm_migrate fails,
logs are collected from when the first test ran (when the VM was
created), not just from the failing test start time.

This solves the issue where class-scoped fixtures create resources
(like VMs) during the first test, but later test failures only collect
logs from that specific test, missing earlier logs.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

<!-- full-ticket-url needs to be provided. This would add a link to the
pull request to the jira and close it when the pull request is merged
If the task is not tracked by a Jira ticket, just write "NONE".
-->

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

* **New Features**
* Configurable data-collection scope via a pytest marker, applied
module-wide across many test modules.
* Must-gather timer now includes a 5-minute buffer when a test start
time is available.

* **Bug Fixes / Reliability**
* Safer start-time storage/retrieval with guards and unified error-aware
handling; improved diagnostic log prefixes.

* **Tests**
* Unit tests updated to cover start-time insert/retrieval and
missing-entry behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 691acbf9-0a5d-4b92-bbe1-7f8572598191

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ 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-5
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:

  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

  • RoniKishner
  • SamAlber
  • SiboWang1997
  • akri3i
  • dshchedr
  • geetikakay
  • jerry7z
  • kbidarkar
  • rnetser
  • vsibirsk
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 automatically removed on each new commit
  • 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.

@dshchedr
Copy link
Copy Markdown
Collaborator Author

/build-and-push-container

@openshift-virtualization-qe-bot-4
Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-4293 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.

4 participants