[ci-fix] test: add 15s timeout to analyze dependency-risks settings-404 test#418
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Conversation
…n Windows
The test 'exits with code 1 when project does not exist (settings 404)'
was missing an explicit timeout option and relied on Bun's default 5000ms.
On the Windows CI runner it took 5049ms — just 50ms over the limit — causing
a spurious failure. Adjacent tests already use { timeout: 15000 }; applying
the same value here makes the suite consistent and prevents the flap.
Fixes: Build run 27197141869
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.
Diagnosis
Category: Test failure (flaky timeout)
The Windows CI job
Integration and E2E Tests - windowsfailed on commit9e6cb01with a single test timeout:The test ran for 5049ms, just 50ms over Bun's default 5000ms timeout. The same test passed on the Linux runner. The adjacent tests in the same file already specify
{ timeout: 15000 }— this test was simply missing the override.Failed run: https://github.com/SonarSource/sonarqube-cli/actions/runs/27197141869
Fix
Added
{ timeout: 15000 }to the'exits with code 1 when project does not exist (settings 404)'test, matching the timeout already used by the two surrounding tests inanalyze-dependency-risks.test.ts. No logic changes.