Repeated self-hosted runner disconnects in SciMLOperators downstream LinearSolve cell
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 45/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- github-actions, julia
- Ambito
- ci-cd, infrastructure
Direzione di ricerca
Inizia con i sei job falliti collegati e l'esecuzione di controllo riuscita, concentrandoti su Downstream LinearSolve.jl/InterfaceII / Downstream Tests - InterfaceII e sul workflow riutilizzabile SciML/.github/.github/workflows/downstream.yml@v1. Ispeziona il servizio del self-hosted runner, il relativo ciclo di vita, la rete, CPU/memoria e i log OOM in corrispondenza dei timestamp elencati; il lavoro è completato quando viene identificata la causa della disconnessione del runner oppure vengono documentate le evidenze rilevanti e la remediation.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Julia
- Stelle
- 6
- Fork
- 5
- Merge medio
- 17g 13h
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di SciML/.github
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 61/100
-
Difficoltà 3/5 Mezza giornata Idoneità per principianti 45/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
Tutte le issue di SciML/.github
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
documentation invalid
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
JuliaPhysics/BeamletOptics.jl#190 ·
I maintainer di solito rispondono entro 1 giorno
-
mul! with a Symmetric or Hermitian factor throws for a matrix view whose columns are not contiguousForse già presa @dkarrasch l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
JuliaLang/LinearAlgebra.jl#1829 ·
I maintainer di solito rispondono entro 1 giorno
-
`EnsembleSummary` `ci_type = :SEM` ribbon is `sqrt(N)` too wide for scalar statesForse già presa @isaacsas l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
SciML/SciMLBase.jl#1654 ·
I maintainer di solito rispondono entro 3 giorni