Skip to content

TEST: avoid cancelling scenario resume for slow database reads - #3138

Merged
Richard Lundeen (richlundeen) merged 2 commits into
microsoft:mainfrom
richlundeen:richlundeen-scenario-resume-timeout
Oct 12, 2026
Merged

Richard Lundeen (richlundeen) merged 2 commits into
microsoft:mainfrom
richlundeen:richlundeen-scenario-resume-timeout

Conversation

@richlundeen

@richlundeen Richard Lundeen (richlundeen) commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Description

Fix a test timeout from #3122's macOS Python 3.11 dev_all job.

The first run completed all three mock attacks and raised the two expected partial failures. The persisted FAILED state and first attempt checks passed. On the second run, the test's 10-second asyncio.wait_for cancelled the completed-objective database read before resumed attacks started. The traceback ends in aiosqlite rollback during read-session close, not in the mock attack's intentional TimeoutError or its event barriers. The logs do not identify why the database operation took this long.

Replace both per-run cancellation limits with direct awaits and one 60-second pytest watchdog. The watchdog still bounds deadlocks and gives thread stacks on expiry. Keep every concurrency barrier, partial-failure check, persisted state transition, attempt count, unfinished-objective batch, and unique-result assertion. No production behavior changes. This PR does not change #3122's branch or the SQLite timing tests covered by #3121.

Use a whole-test watchdog instead of ten-second per-run cancellation limits. Preserve concurrent partial failure, persisted state, and duplicate-free resume checks.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 50e6571a-68d7-4399-a2f0-a2dfc6cc6ff9
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 69d98770-b1a5-4feb-a16c-00b604a5f982
@richlundeen
Richard Lundeen (richlundeen) added this pull request to the merge queue Oct 12, 2026
Merged via the queue into microsoft:main with commit 8574961 Oct 12, 2026
51 checks passed
@richlundeen
Richard Lundeen (richlundeen) deleted the richlundeen-scenario-resume-timeout branch October 12, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants