Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Repeated self-hosted runner disconnects in SciMLOperators downstream LinearSolve cell

オープン
#116 コメント 9 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
静か
技術スタック
github-actions, julia

調査の方向性

リンクされた6件の失敗したジョブと成功したコントロール実行から始め、Downstream LinearSolve.jl/InterfaceII / Downstream Tests - InterfaceII と再利用可能な workflow SciML/.github/.github/workflows/downstream.yml@v1 に焦点を当てます。記載されたタイムスタンプ前後の self-hosted runner サービス、ライフサイクル、ネットワーク、CPU/メモリ、および OOM ログを調査します。完了条件は、runner の切断原因を特定するか、関連する証拠と対処を文書化することです。

索引モデルが issue の本文から書いたものです。

説明

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.

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.

主要言語
Julia
スター
6
フォーク
5
平均マージ
17日 13時間
マージ済み PR(30日)
1

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

SciML/.github のほかの issue

SciML/.github の issue をすべて見る

似ている issue

Julia の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。