E2E iOS: the camera permission test and the first userEvent.type test take up to 10 s on the macOS runner and time out at the playground's 10 s testTimeout
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 58/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, react-native, typescript
Línea de trabajo
Start with apps/playground/rn-harness.config.mjs and the named tests in permissions.harness.tsx and type.harness.tsx; compare their timing diagnostics from the linked iOS workflow runs to see where the time is spent. Identify why the first camera permission and userEvent.type tests approach the 10 s timeout, then verify the E2E iOS workflow no longer fails intermittently from those timeouts.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
On the E2E workflow's iOS job, two playground tests run up to the playground's 10 s testTimeout (apps/playground/rn-harness.config.mjs; the workflow sets no HARNESS_TEST_TIMEOUT) and fail now and then with Test timed out after 10000ms:
permissions.harness.tsx› "should allow camera permissions when requested", which itself waits up to 30 s for the permission (waitUntil(() => latestStatus === 'authorized', { timeout: 30000 }))type.harness.tsx› "should type text into TextInput and trigger onChangeText", the run's firstuserEvent.type
Their durations, from each run's harness-diagnostics-e2e-ios artifact:
| Run | Head | Camera permission test | First userEvent.type test |
|---|---|---|---|
| 40528303747 | #249 | 4970 ms | 2519 ms |
| 40535898599 | #298 | 6218 ms | 5730 ms |
| 40291893624 | ci/host-health-telemetry |
9487 ms | 6016 ms |
| 40528307146, attempt 1 | #257 | 10099 ms, timed out | 8062 ms |
| 40528307146, attempt 2 | #257 | 9043 ms | 4813 ms |
| 40868510310 | main 26b67ea |
7805 ms | 6308 ms |
| 40869641948 | main 26b67ea |
9946 ms | 4085 ms |
| 40869661561 | main 26b67ea |
5864 ms | 3834 ms |
| 40873698792 | main 26b67ea |
5415 ms | 5749 ms |
| 40873708733 | main 26b67ea |
10180 ms, timed out | 4053 ms |
| 40873717208 | main 26b67ea |
7753 ms | 10376 ms, timed out |
| 40873726063 | main 26b67ea |
10123 ms, timed out | 8626 ms |
The other userEvent.type tests take about a second each, so the first one pays for something the rest reuse. Four ci/host-health-telemetry runs on Oct 26 (40353077744, 40316171106, 40313220029, 40298624538) failed the camera test the same way.
System Info
GitHub Actions macos-latest: 3 cores, 7 GB, arm64, macOS 26 (osRelease 25.6.0), ImageOS macos26, ImageVersion 20261013.0424.1
Xcode 26.4.1, Node.js 24.10.0
React Native Harness Version
1.6.0 (main at 26b67ea)
Reproduction
https://github.com/YevheniiKotyrlo/react-native-harness/actions/runs/40873708733 (the E2E workflow on my fork's main, at 26b67ea)
Steps to reproduce
- Run the E2E workflow on
mainwithplatform: ios(I dispatched it on my fork'smain, synced to 26b67ea). - Three of my seven runs failed on one of the two tests with
Test timed out after 10000ms, as the table shows; the rest passed with both at 3.8–9.9 s.
Expected: both tests finish within the test timeout on every run, or carry a timeout that covers the waits they make.
Actual: three of seven runs failed on one of them with Test timed out after 10000ms.
- Lenguaje dominante
- TypeScript
- Estrellas
- 335
- Forks
- 23
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 54
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstackincubator/react-native-harness
-
On Windows, `report.test.ts`'s unwritable-folder case creates `\dev\null\nope` at the drive root instead of meeting an unwritable folderPosiblemente ocupada @TheSeydiCharyyev la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
callstackincubator/react-native-harness#301 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
callstackincubator/react-native-harness#296 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
callstackincubator/react-native-harness#128 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
callstackincubator/react-native-harness#300 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
callstackincubator/react-native-harness#299 ·
Los mantenedores suelen responder en 1 día
Todos los issues de callstackincubator/react-native-harness
Issues similares
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Export the Hemi Earn Router address and the Router and Agent ABIs from `@vetro-protocol/earn`Abiertohemi-earn
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
vetro-protocol/vetro-monorepo#1043 ·
Los mantenedores suelen responder en 1 día
-
stage 2: bare names resolve against PATH differently from the shell (empty and relative entries)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
STRML/omp-classifier#206 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
atlassian-labs/mermaid-diagrams-viewer#188 ·
Los mantenedores suelen responder en 1 día
-
dashboard enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Olanetsoft/agent-lookout#225 ·
Los mantenedores suelen responder en 1 día