Repository navigation
test(ui): repair and retire all six quarantined suites - #14493
Merged
diegosouzapw merged 1 commit intoSep 24, 2026
Merged
Conversation
diegosouzapw
changed the base branch from
fix/qg10-quarantine-contract-20260922
to
release/v3.8.51
September 24, 2026 00:57
diegosouzapw
force-pushed
the
fix/qg10-quarantine-retirement-20260922
branch
from
September 24, 2026 00:57
cc9201a to
0fb779f
Compare
diegosouzapw
marked this pull request as ready for review
September 24, 2026 00:57
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
) (#14415) Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada). Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`: - 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359) - `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511) - eslint nos arquivos alterados limpo; file-size OK
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
…h a one-shot bootstrap token (#14296) (#14472) Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada). Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`: - 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359) - `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511) - eslint nos arquivos alterados limpo; file-size OK
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada). Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`: - 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359) - `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511) - eslint nos arquivos alterados limpo; file-size OK
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
Merge-batch 2026-09-23 (PRs do mantenedor, Trilha B, retrabalhada). Um worker corrigiu o defeito apontado na revisão direto no branch da PR; o detalhe está na seção "Rework (merge-batch 2026-09-23)" do corpo, com a prova de red→green. Revalidado numa árvore combinada das PRs da 2ª leva da Trilha B (#14415 #14472 #14468 #14493 #14403) sobre o tip atual de `release/v3.8.51`: - 104/104 testes node focados + 46/46 vitest (as 6 suítes de UI que saíram da quarentena); `check:provider-consistency` OK (359) - `typecheck:core`: só o herdado `cliproxyAccountHealth.ts:157`; `check:open-sse-typecheck`: só o herdado `auggie.ts` (base-red #14547, corrigido pela #14511) - eslint nos arquivos alterados limpo; file-size OK
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
All three fail on the release tip (fast-path shards 3/4 and 4/4 of #14718, a PR that touches none of their subjects) and no open base-red PR covers them. Each follows an intentional product change that merged without its guard: - responses-handler: #14572 (#14330) gave the synthesized response.in_progress keepalive a sequence_number and response object; the assertion now pins the full compliant frame instead of the bare one. - check-vitest-exclusions: #14493 repaired every quarantined suite and emptied the inventory; the live-config test still fails on any exclusion the inventory does not list, so the non-empty check was the only stale part. - perf-waterfall-elimination: #14421 routes the Home settings read through loadHomeSettings() (defaults to getSettings); the test still requires it in the same Promise.all batch, before getMachineId, with no serial await. 28/28 on the idle .113. Refs #14547
adivekar-utexas
added a commit
to adivekar-utexas/OmniRoute
that referenced
this pull request
Sep 24, 2026
Four independent pieces of release-branch drift were red on every PR to release/v3.8.51, none of them caused by this PR. Fixing each per what its own gate message prescribes: - .env.example + docs/reference/ENVIRONMENT.md: document DEEP_HEALTH_CHECK_ENABLED (read by src/app/api/monitoring/health/route.ts) — check:env-doc-sync reported 'In code but missing from .env.example: 1'. - config/quality/dependency-allowlist.json: allowlist @opencode/plugin (npm v2.0.16, publisher thdxr <d@ironbay.co>, the opencode maintainer). The pre-existing @opencode-ai/plugin entry is the old scope; upstream renamed it. Verified against the registry before allowlisting, per check:deps' human-review requirement. - tests/unit/check-vitest-exclusions.test.ts: drop the 'inventory is not empty' fixture precondition. vitest-exclusions.json's excluded:[] is the healthy end state after cheaper-inference#14493 returned all six quarantined files to normal discovery, so the assertion is stale; the per-entry loop already validates whatever entries exist.
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
All three fail on the release tip (fast-path shards 3/4 and 4/4 of #14718, a PR that touches none of their subjects) and no open base-red PR covers them. Each follows an intentional product change that merged without its guard: - responses-handler: #14572 (#14330) gave the synthesized response.in_progress keepalive a sequence_number and response object; the assertion now pins the full compliant frame instead of the bare one. - check-vitest-exclusions: #14493 repaired every quarantined suite and emptied the inventory; the live-config test still fails on any exclusion the inventory does not list, so the non-empty check was the only stale part. - perf-waterfall-elimination: #14421 routes the Home settings read through loadHomeSettings() (defaults to getSettings); the test still requires it in the same Promise.all batch, before getMachineId, with no serial await. 28/28 on the idle .113. Refs #14547
Witroch4
pushed a commit
to Witroch4/OmniRoute
that referenced
this pull request
Oct 24, 2026
… the discovery suite With @testing-library/dom installed the six remaining RTL suites load. Three cache component suites (CachePerformance, CacheTrends, IdempotencyLayer) still asserted an old markup; upstream repaired them and moved them to tests/unit/ui/cache/ in cheaper-inference#14493 (2697760). Those versions pass 40/40 against the fork's components, so they replace the stale copies. DiscoveryPageClient used jest-dom matchers without importing them. vitest.config.ts: 244 files / 1734 tests green (was 51 failing files). Co-Authored-By: Claude Opus 5.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.
Scope
Stacked on #14426. Repairs and returns all six quarantined files to the normal UI test collector; the exclusion inventory becomes empty. No expiry extension, threshold reduction, production mock replacement or dropped assertion.
tests/unit/ui/cache/and load their DOM assertion matchers.Evidence
vitest.config.ts: 50/50 in seven files (the six repaired files plus the adjacent four-test cache-settings suite selected by the path).check-test-discovery: 6155 files, 32 collectors, zero quarantined files. Nine already-frozen orphan files remain separate debt.Local focused runs used the available Vitest 4.1.11 tooling. The lockfile-pinned Vitest 5 CI on the combined candidate remains required; this draft is not full release acceptance.
Resgate para release/v3.8.51 (merge-batch 2026-09-23)
Esta PR estava empilhada sobre
fix/qg10-quarantine-contract-20260922(#14426), que não vai para a release. A base foi trocada pararelease/v3.8.51e o branch foi reconstruído a partir do tip da release (adefe4f5).cc9201a9"test(ui): repair and restore all quarantined component suites", re-aplicado como0fb779f1(o único commit próprio desta PR).owner/expires),vitest.quarantine.config.tse o workflow.github/workflows/test-quarantine.yml..github/workflows/test-quarantine.yml: descartado, porque o arquivo só existe em ci: make quarantined test debt bounded and executable #14426.config/quality/vitest-exclusions.json: a versão da release já tem o inventário (semowner/expires). O resgate zeraexcluded: [], echeck:vitest-exclusionspassa com "0 excluded file(s)".tests/unit/ui/cache/, as exclusões retiradas dovitest.config.tse o inventário zerado.npx vitest run --config vitest.config.tsnas 6 suítes deu 46/46 (6/6 arquivos).react/jsx-runtimee 1 teste. Isoladas e com a carga menor, deram verde duas vezes seguidas.