Repeated self-hosted runner disconnects in SciMLOperators downstream LinearSolve cell
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- github-actions, julia
- Área
- ci-cd, infrastructure
Línea de trabajo
Comienza con los seis jobs fallidos enlazados y la ejecución de control exitosa, centrándote en Downstream LinearSolve.jl/InterfaceII / Downstream Tests - InterfaceII y el workflow reutilizable SciML/.github/.github/workflows/downstream.yml@v1. Inspecciona el servicio del self-hosted runner, su ciclo de vida, la red, la CPU/memoria y los logs de OOM alrededor de las marcas de tiempo indicadas; se considera terminado cuando se identifica la causa de la desconexión del runner o se documentan las pruebas relevantes y la remediación.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
The LinearSolve.jl/InterfaceII cell in SciMLOperators' downstream workflow has repeatedly ended because its self-hosted runner lost communication with GitHub Actions. This is an infrastructure issue: the affected job has no Julia test failure to debug, and the same workflow cell later passed on unchanged workflow configuration.
Affected cell:
Downstream LinearSolve.jl/InterfaceII / Downstream Tests - InterfaceII
The workflow invokes SciML/.github/.github/workflows/downstream.yml@v1.
Affected runs
GitHub attached the same runner-level annotation to the LinearSolve cell in each run:
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
- https://github.com/SciML/SciMLOperators.jl/actions/runs/29223216729 (job
86732259844, commitbd79a08a8f25c06cf5df8c5c8251141c84618665) - https://github.com/SciML/SciMLOperators.jl/actions/runs/29221485099 (job
86727335539) - https://github.com/SciML/SciMLOperators.jl/actions/runs/29208191777 (job
86691212542) - https://github.com/SciML/SciMLOperators.jl/actions/runs/29014025369 (job
86104381113) - https://github.com/SciML/SciMLOperators.jl/actions/runs/29013087868 (job
86101254571) - https://github.com/SciML/SciMLOperators.jl/actions/runs/29012530820 (job
86099385760)
In run 29223216729, the downstream test step was still reported as in_progress when the job closed. The job log blob now returns 404, so there is no package-level exception or failed assertion available to investigate. That run started at 2026-07-13 04:11:26 UTC and ended at 04:39:28 UTC.
Control run and bisectability
The same cell passed in https://github.com/SciML/SciMLOperators.jl/actions/runs/29235992715, which started at 2026-07-13 08:35:48 UTC and completed at 08:59:24 UTC. Its log contains substantive Test Summary output. The SciMLOperators commits between the failed run and this green run did not change the downstream workflow or its LinearSolve dependency configuration.
There is therefore no source commit to bisect for these disconnects: GitHub reports termination outside the Julia test process, and the same reusable workflow/cell subsequently completed successfully without a relevant source or workflow fix.
Requested investigation
Please inspect the self-hosted runner service, lifecycle, network connectivity, and resource/OOM logs around the affected timestamps. In particular, it would be useful to determine why this LinearSolve downstream cell repeatedly loses its runner after roughly 20–30 minutes while sibling downstream cells complete.
This issue intentionally tracks only the runner disconnects. Any downstream group-selection cleanup should be handled separately.
- Lenguaje dominante
- Julia
- Estrellas
- 6
- Forks
- 5
- Merge medio
- 17 d 13 h
- PR fusionados (30 d)
- 1
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 SciML/.github
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 61/100
-
Dificultad 3/5 Medio día Aptitud para principiantes 45/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
Todos los issues de SciML/.github
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
documentation invalid
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
JuliaPhysics/BeamletOptics.jl#190 ·
Los mantenedores suelen responder en 1 día
-
mul! with a Symmetric or Hermitian factor throws for a matrix view whose columns are not contiguousPosiblemente ocupada @dkarrasch la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
JuliaLang/LinearAlgebra.jl#1829 ·
Los mantenedores suelen responder en 1 día
-
`EnsembleSummary` `ci_type = :SEM` ribbon is `sqrt(N)` too wide for scalar statesPosiblemente ocupada @isaacsas la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
SciML/SciMLBase.jl#1654 ·
Los mantenedores suelen responder en 3 días