[cli-tools-test] [CLI exploratory testing] Windows deprecated missing-tool key fails strict dry-run gate

オープン 初心者向け
  • 何か問題がありますか？
#74,755 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
70/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, go
領域
ci-cd

調査の方向性

.github/workflows/windows.mdの54行目あたりを読み、信頼できるworkflowのサンプルが安全な出力をどのように設定しているか確認してください。非推奨のキーmissing-toolをreport-missing-toolに移行し、その後、厳格なdry-run設定でWindows workflowをコンパイルして、再生成されたwindows.lock.ymlを確認してください。バッチ警告ゲートを通過し、lockファイルに更新後のworkflowが反映されていれば完了です。

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

説明

automation cli-tools testing
Overview

Bounded testing on 2026-11-04 found that .github/workflows/windows.md:54 uses the deprecated missing-tool safe-output key. Its strict dry-run compile emits a lock but fails the overall warning gate. Severity: Low; observed once. This is a repository workflow compatibility issue, not evidence that the safeguard should be weakened.

Reproduction
  1. On github/gh-aw, invoke agenticworkflows MCP compile with workflows=[windows], dry_run=true, strict=true.
  2. Inspect both workflow and batch results.
  3. The workflow result is valid and identifies windows.lock.yml, but the compiler batch is invalid and dry_run.gate is failed.

Expected: the maintained trusted sample uses current settings and passes the strict gate. Actual diagnostic: The missing-tool safe-output key is deprecated. Use report-missing-tool instead.

Proposed correction: migrate the setting through normal workflow maintenance, then compile and review the regenerated lock. No workflow source was edited by this tester.

Diagnostics and bounded coverage

Passed checks

  • Discovery returned 356 workflows, all marked compiled. Sampled triggers and imports matched the selected sources; freshness was not independently established.
  • Five logs queries, always count=3: last day; daily-workflow-security-model over seven days; copilot engine over one day; nonexistent-workflow-xyz; future date 2099-01-01. Exposed JSON summaries were readable. Nonempty results had at most three runs and consistent IDs, workflow names, engines, statuses and timestamps. Unknown workflow returned actionable guidance; future date returned zero runs. Count-limited results warned about partial coverage.
  • Two completed-run audits: failed Daily Workflow Security Model and successful PR Finisher. Metadata agreed with logs. Reports exposed job timing, metrics and safe-output summaries; the success sample exposed bash and safeoutputs.noop calls, MCP health, and 24 network requests. Its noop described unfinished task work, so workflow success is not task completion. Neither sample created GitHub resources. Invalid audit ID 0 returned clear guidance.
  • Windows emitted a local lock with frontmatter/body hashes, strict/dry-run metadata, expected job sections and staged safe outputs; ShellCheck passed with zero added findings. This was structural inspection, not independent complete Actions validation.
  • Logs took approximately 7.5–9.7 seconds for nonempty queries and 1.5 seconds for the future date. Audits took 11.0 and 9.4 seconds. Compiles took 0.9–2.7 seconds. These are single observations.

Observed problems

Windows failed the batch warning gate on the deprecated key. A per-workflow valid result must not be interpreted as an overall gate pass. The tool also warned that cached model inventory may be stale.

Blocked or unfinished required checks

All three targeted compiles used dry_run=true and strict=true; zero passed the overall gate. Archie was rejected for pre-agent steps and custom MCP servers. Daily Workflow Security Model was rejected for custom steps. These safeguard denials were not retried or worked around. Passing complex/import compilation, corresponding generated-lock inspection, and compile-to-existing-run integration remain unverified. The failed existing run used SHA f3dc4385203cb61f4ebc410546ee91822538e884; it does not validate a newly generated lock.

Not tested (expected exclusion)

  • Malformed YAML, invalid tool configuration and missing imports: synthetic fixtures prohibited.
  • Private raw logs, raw directory structure and independent artifact completeness: outside scope.
  • Execution of newly compiled locks: dispatch prohibited.
  • Historical/retention and in-progress audit variants: outside the two completed-run sample.
  • Redundant date variants and incremental recompilation: optional variants omitted after failed compile gates.
  • Created-resource links and failed sub-agent attribution: not exercised by these samples.
Next actions

Migrate the Windows setting and review which trusted samples satisfy the existing safeguards. Required compile coverage is incomplete and is being reported separately. No locks were published, pushed or executed. This sample does not establish repository-wide CLI health.

References:

Generated by 🧪 Daily Cli Tools Tester · codex · gpt60 · ~155 AIC · ⌖ ~57 AIC · ⊞ 21.2K · ◷

  • expires on Nov 10, 2026, 9:23 PM UTC-08:00
主要言語
Go
スター
5.6k
フォーク
615
平均マージ
5時間 51分
マージ済み PR（30日）
793

環境構築

Codespaces で開く

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

はじめの一歩

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

github/gh-aw のほかの issue

github/gh-aw の issue をすべて見る

似ている issue

Go の issue をもっと見る

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

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