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

Solution runner can exceed the configured timeout and keep CI running

Cerrado
  • ¿Algo no está bien?
#17 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@vivek-3728 ya está trabajando en esto.

Desde el 9/10/2026.

  • #24 de @vivek-3728 — fusionado

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
backend, ci-cd

Línea de trabajo

Start by reading run.py and the GitHub Actions workflow; trace how the per-test timeout is applied and how compilation is launched. Run the existing test suite and inspect how the runner handles timed-out processes. Done means compilation and total execution have separate limits, spawned processes are cleaned up, and the workflow has an appropriate job timeout.

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

Descripción

advanced bug

I noticed that the solution runner doesn't properly limit how long a submitted solution can run.

The configured timeout is applied separately to each test case rather than to the solution's total execution time. Compilation also doesn't appear to have any timeout.

For example, I tested four cases that each took around 0.35 seconds. All four passed with a configured timeout of just 1 second, even though the total execution took approximately 1.55 seconds.

With the current behavior, 100 test cases and a 10-second timeout could potentially keep a solution running for around 1,000 seconds. A compilation process that hangs could also block the runner indefinitely.

I expected the runner to enforce an overall execution limit so that a submitted solution couldn't occupy CI resources for much longer than intended.

Looking through run.py, the timeout is applied inside the loop that executes individual test cases, while the compilation step has no timeout. The GitHub Actions workflow also doesn't define a job-level timeout.

This could become a bigger problem with submissions that run slowly, generate excessive output, or start additional processes.

It would be useful to enforce separate compilation and overall execution limits, along with proper cleanup of spawned processes and safeguards against excessive resource usage.

Lenguaje dominante
Python
Estrellas
1
Forks
6
Merge medio
17 h 52 min
PR fusionados (30 d)
14

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 techcsispit/code-corner

Todos los issues de techcsispit/code-corner

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.