Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

iOS runner: isolate collapsed-tab occupancy test from prerequisite timeouts

Abierto
  • ¿Algo no está bien?
#3,800 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
49/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ios, typescript
Área
mobile, testing

Línea de trabajo

Start with RunnerTests+SnapshotCapturePlanOccupancyTests.swift near line 529 and inspect the test’s fixture and the prerequisite viewport, orientation, keyboard, and tree-processing steps. Build a focused reproduction that detects an unintended prerequisite timeout, then verify the corrected fixture passes while retaining the delayed-operation assertion, expected budget reason, and truncated-tree refusal. Run the owning iOS test lane.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Purpose

Make the collapsed-tab occupancy test exercise its intended exhausted tree tier on slow CI hosts.

testPlanMovesPastATreeTierWhoseCollapsedTabQueryCannotStart expects reason budget. It sometimes receives capture-failed at RunnerTests+SnapshotCapturePlanOccupancyTests.swift:529.

Evidence

The raw job logs show the same assertion on three unrelated heads:

The test file is identical across these heads. #3791 changes no Swift file. Its new daemon timing step runs after the XCTest suite.

The #3791 log records a one-second snapshot_viewport timeout before private AX recovery. The other failures record a tree-processing timeout. These paths produce capture-failed before the intended budget assertion. Host timing is a suspected trigger; it is not a proven complete cause.

A focused local loop passed 3/3 times on a separate iOS 26.2 simulator. No local red reproduction or fix is proven.

Required behavior

  • Isolate prerequisite viewport, orientation, keyboard, and processing work from the deliberately delayed tree operation.
  • Preserve the assertion that the delayed operation was entered.
  • Preserve the expected budget reason and the refusal to accept a truncated tree as healthy.
  • Use a deterministic fixture or injected facts. A warm-up read alone must not claim to prevent a later timeout.
  • Do not widen timeouts, add retries, skip the test, or accept both reason codes.

Completion

Show a focused reproduction that detects the unintended prerequisite timeout. Then show the corrected fixture passes and still detects the intended regression. Run the owning iOS lane.

Owner: the iOS runner test lane. Related: #2847 and #2957. Keep this fix separate from #3791's daemon startup contract.

Lenguaje dominante
TypeScript
Estrellas
5k
Forks
334
Merge medio
12 h 14 min
PR fusionados (30 d)
713

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.