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

CI: Intel macOS main suite hits 45-minute limit after the [99i] compile audit

クローズ
#1,261 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

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

評価

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

調査の方向性

Start with tests/run_all_tests.sh around line 8199 and the macOS workflow in .github/workflows/ci.yml around line 684. Reproduce the main-push lane with [99i] enabled and inspect the Intel logs to attribute the outstanding selftest work. Done means a complete Intel suite followed by the LSP check while retaining the intended platform coverage and fault controls.

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

説明

area:ci kind:gate-defect

Two consecutive main runs on macos-15-intel hit the 45-minute job limit after the [99i] compiler audit prints its successful 585-invocation result. This prevents a complete Intel macOS verdict for the M1 candidate.

Observed runs (UTC, 2026-09-22):

Commit / job [99i] starts Audit reports 585 invocations Cancellation
bb33420, 106623379646 05:26:37 05:35:52 05:53:40
d7f227a, 106880174185 18:50:26 18:59:47 19:13:39

Both check-run annotations explicitly report that the job exceeded 45 minutes. The second job started at 18:28:23, with its main suite starting at 18:29:53. It passed all 15 [99e] SIGUSR1 checks before reaching [99i]. ARM macOS and every other job in that main CI run completed successfully.

At this revision, the suite runs the audit followed by --selftest, capturing selftest output until completion. There is no final [99i] PASS or suite RESULTS line in either Intel log. The available logs do not distinguish a stalled child from cumulative work exceeding the remaining budget; there is no child stack or per-control timing evidence.

The macOS workflow intentionally includes [99i] on main to exercise BSD-userland portability. Its PR lane delegates the audit to Linux, so green PR checks cannot establish completion of this Intel path.

Local serial runs of the candidate passed the complete audit plus selftests: [99i] took 2063.05 seconds in the release suite and 1775.72 seconds in the ASan/UBSan HTTP suite. Whole-suite results were 5350/5350 and 6127/6127 respectively. These are Linux observations, not an Intel macOS diagnosis.

Reproduction: the existing main-push CI lane at either linked commit, with [99i] enabled. No workflow changes, timeout increase or rerun was used in this investigation.

Resolution needs attribution of the outstanding selftest work and a completed Intel suite plus subsequent LSP check while retaining the intended platform coverage and fault controls. This is a distinct observation from #1126's older [99e] stop; it also follows the CI ownership work in #1160.

主要言語
C
スター
3
フォーク
7
平均マージ
4時間 15分
マージ済み PR(30日)
106

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

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

InauguralSystems/EigenScript のほかの issue

InauguralSystems/EigenScript の issue をすべて見る

似ている issue

C の issue をもっと見る

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

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