test: Runtime suite can exceed the 60-second CI timeout

Abierto
#68 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
62/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start with the Release Runtime workflow’s 60-second test-session timeout and the RaceTrackerBoundsTests cases listed in the issue; compare the slow CI run with the successful run to locate whether runtime or test configuration is responsible. Check the Runtime test command and its timeout settings. Done means the suite completes reliably with headroom for hosted-runner variance, or the configured timeout is increased to provide it.

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

Descripción

Summary

The Release Runtime test step can time out at the workflow's 60-second test-session limit without any test failure.

Evidence

CI run https://github.com/ReubenBond/Clockwork/actions/runs/44226678257 reached 1,200 succeeded tests, 0 failed, and 0 skipped before Microsoft Testing Platform canceled the session at 59.9 seconds with exit code 3.

The remaining active cases were in RaceTrackerBoundsTests, including:

  • ContinuationChainKeepsStateBoundedAndReportsARaceAtItsEnd(chain: Delay)
  • ContinuationChainKeepsStateBoundedAndReportsARaceAtItsEnd(chain: AwaitOwnCompletion)
  • RepeatedAwaitedFanOutOverFreshObjectsKeepsStateBounded

The preceding CI run completed the same Runtime step successfully in approximately 33 seconds, so this appears sensitive to hosted-runner performance.

Expected behavior

The Runtime suite completes reliably within its configured CI test-session timeout, or the timeout provides sufficient headroom for normal hosted-runner variance.

Scope

This was observed while validating #62 and is unrelated to that PR's package-layout changes.

Lenguaje dominante
C#
Estrellas
0
Forks
0
Merge medio
2 h 32 min
PR fusionados (30 d)
23

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 ReubenBond/Clockwork

Todos los issues de ReubenBond/Clockwork

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.