Skip to content

test(engine): align goroutine leak tolerance with the rest of the suite - #154

Open
mendsec wants to merge 1 commit into
developfrom
fix/m5-leak-tolerance
Open

mendsec wants to merge 1 commit into
developfrom
fix/m5-leak-tolerance

Conversation

@mendsec

@mendsec mendsec commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Rebase do #147 sobre o develop atual.

O #145 já entregou as demais mudanças daquele PR (callbackDelay de 20ms, report.EndTime.Sub(start), comentário corrigido). Sobrou uma linha.

TestNoGoroutineLeakOnPrematureCancel usava leak > 2, enquanto todos os outros checks de vazamento da base permitem 3 — scan_test.go:206 no mesmo arquivo e scanner_test.go:101. Isto alinha o outlier.

Fecha #147.

TestNoGoroutineLeakOnPrematureCancel used "leak > 2" while every other
leak check in the codebase allows 3: scan_test.go:206 (before+3) in the same
file, and scanner_test.go:101 (leak > 3). This makes it consistent.

Rebased from #147 onto current develop; the other changes in that PR had
already landed via #145.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 1 duplication

Metric Results
Complexity 0
Duplication 1

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@github-actions
github-actions Bot deleted the fix/m5-leak-tolerance branch September 13, 2026 03:11
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