Repository navigation
fix: give the device-cap session test a CPU-bound timeout - #16
Merged
Merged
Conversation
The test performs 11 bcrypt hashes at 12 salt rounds; slow CI runners can exceed the default 5s vitest timeout (observed on PR #13 run 30818649435). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sessionSecurity.test.ts > caps active devices and revokes the oldest sessionperforms 11 bcrypt hashes at 12 salt rounds (register + 10 logins). On slow CI runners this exceeds vitest's default 5s test timeout — observed as a flake on PR #13 (run 30818649435) while the suite passes locally in ~5.0s. Give the test an explicit 30s budget.Test plan
pnpm exec vitest run src/sessionSecurity.test.ts— 3 passed🤖 Generated with Claude Code