Consistently use mut marker for tests that write to the database#290
Consistently use mut marker for tests that write to the database#290
mut marker for tests that write to the database#290Conversation
WalkthroughThis change updates pytest markers across several test modules. The
The 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@tests/routers/openml/study_test.py`:
- Line 461: The test module uses the `@pytest.mark.mut` decorator but never
imports pytest, causing NameError during collection; add a top-level import for
pytest (i.e., import pytest) in the same test file that contains the
`@pytest.mark.mut` usages so the decorator resolves (search for occurrences of
`@pytest.mark.mut` to locate the affected module).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 71e844be-d238-43b4-b13c-4ee032635c4b
📒 Files selected for processing (7)
tests/routers/openml/dataset_tag_test.pytests/routers/openml/datasets_test.pytests/routers/openml/migration/datasets_migration_test.pytests/routers/openml/migration/flows_migration_test.pytests/routers/openml/migration/setups_migration_test.pytests/routers/openml/qualities_test.pytests/routers/openml/study_test.py
💤 Files with no reviewable changes (1)
- tests/routers/openml/migration/flows_migration_test.py
Even within a transaction, as some requests may stall until transactions with write requests are committed/aborted.