Skip to content

test: stop a timing check failing on a busy CI runner - #1147

Merged
1 commit merged into
stagingfrom
fix/wrapped-components-timing
Nov 6, 2026
Merged

1 commit merged into
stagingfrom
fix/wrapped-components-timing

Conversation

@tirth8205

Copy link
Copy Markdown
Owner

test_thousands_of_wrapped_components_in_one_scope came in with #972 through #1146. It took 24.6s against a 20s limit on the staging push run, and test (3.12) went red, on the same tree that passed on the PR. A red required check on staging stops the daily promotion.

The test says its bound only exists to catch a blow-up, so this raises it to 90s. No product code changes.

🤖 Generated with Claude Code

test_thousands_of_wrapped_components_in_one_scope took 24.6s against a 20s limit
on the staging push run for #1146, on the same tree that had passed on the PR.
The bound is there to catch a blow-up, so 90s still does that.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

code-review-graph review

Overall risk: 0.05 (LOW) — 1 changed function(s)/class(es), 0 affected flow(s), 0 test gap(s)

Risk-scored changes

Risk Level Symbol Location Tested
0.05 low tests/test_js_wrapped_functions.py::test_thousands_of_wrapped_components_in_one_scope tests/test_js_wrapped_functions.py:1109 (test)

Token savings: this graph-backed report used ~13,606 fewer tokens (~98%) than reading every changed file in full (estimated, chars/4 approximation).


Powered by code-review-graph — local-first analysis; no code leaves the CI runner.

@tirth8205 tirth8205 closed this pull request by merging all changes into staging in 115dccf Nov 6, 2026
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