test: Mark flaky tests with `run_alone` to reduce CI failures by vdusek · Pull Request #1733 · apify/crawlee-python
Mark the following tests with `@pytest.mark.run_alone` so they run in isolation (numprocesses=1) rather than in parallel, reducing flakiness observed across the last 10 master commits: - test_open_and_close_page (failed on Windows) - test_get_cpu_sample (failed on Windows) - test_snapshot_pruning_removes_outdated_records (failed on Ubuntu) - test_execution in test_recurring_task (upgraded from run_alone_on_mac to full run_alone, failed on macOS) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Issues with this label are in the ownership of the tooling team.
Ad-hoc unplanned task added during the sprint.
labels
Feb 11, 2026The test fails with `assert 3 == 2` even when running in isolation, indicating a real bug in snapshot pruning boundary logic rather than a parallelism issue. Tracked in #1734 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Timing-sensitive test fails when running in parallel due to CPU contention (0.312s > 0.3s threshold). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
vdusek
deleted the
test/mark-flaky-tests-run-alone
branch
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