Skip to content

Read the clock once in the edit lock's start-time test - #83

Merged
bonelifer merged 1 commit into
mainfrom
fix-edit-lock-test-time
Oct 15, 2026
Merged

bonelifer merged 1 commit into
mainfrom
fix-edit-lock-test-time

Conversation

@bonelifer

Copy link
Copy Markdown
Contributor

edit_lock_test::test_taking_again_keeps_when_the_editor_started (#77) read the clock once when inserting the row and again when checking it, so it failed whenever a second passed in between. That happened on the SQL Server jobs of #82: 1792037280 is identical to 1792037281. The extra argument meant to allow for it did nothing, as assertSame takes no tolerance. The test now reads the clock once and compares with that.

Claude ran the unit tests on phpBB 3.3: all 331 pass.


Investigated and written by Claude on behalf of William Jacoby (bonelifer).

🤖 Generated with Claude Code

The test compared a time read when the row was inserted with time() read
again at the check, so it failed when a second passed in between, as it
did on a slow SQL Server runner. assertSame takes no tolerance, so the
extra argument meant to allow for that did nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bonelifer
bonelifer merged commit 17c3569 into main Oct 15, 2026
58 checks passed
@bonelifer
bonelifer deleted the fix-edit-lock-test-time branch October 15, 2026 04:30
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.

1 participant