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

Aperta Adatta ai principianti
  • Qualcosa non va?
#75,317 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, go
Ambito
ci-cd, tooling

Direzione di ricerca

Inizia dalla configurazione del workflow windows e individua la sua chiave di output sicuro obsoleta missing-tool; l’issue indica report-missing-tool come sostituzione. Aggiorna la chiave seguendo il normale processo di manutenzione, quindi esegui di nuovo la compilazione rigorosa in modalità dry-run per windows e conferma che siano superati sia il risultato del workflow sia il controllo del batch.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

automation cli-tools testing
Overview

Bounded CLI exploration on 2026-11-06 found a repository workflow configuration problem: windows emits a lock but fails its strict dry-run gate because it uses the deprecated missing-tool safe-output key. Severity: Low; observed once. This is not evidence of a compiler crash.

Reproduction and diagnostics
  1. Invoke agenticworkflows compile with {"workflows":["windows"],"dry_run":true,"strict":true}.
  2. Inspect both the workflow result and batch gate.

Expected: the trusted sample passes strict compilation, or clearly reports required configuration maintenance. Actual: workflow valid: true, followed by batch valid: false and gate: failed. Consumers must inspect the batch result.

Redacted diagnostics

The missing-tool safe-output key is deprecated. Use report-missing-tool instead. The diagnostic appears twice within compiler_warning; no line number was supplied. Shellcheck passed with zero added findings. The emitted lock metadata includes strict: true, dry_run: true, and frontmatter/body hashes.

Passed checks
  • Status discovery returned workflow names, engines, triggers, compilation state, and dependencies (~4.6s); exhaustive enumeration comparison was not performed.
  • Three logs queries, each with count: 3: last day (3 runs), weekly-editors-health-check over seven days (1 run), and copilot over the last day (3 runs). Exposed JSON summaries were readable; sampled names, engines, timestamps, and count limits matched filters. Count-limited responses clearly reported partial coverage. Times: ~9.8s, 6.0s, and 12.5s; the engine query exceeded the 10s aspirational target in this single observation.
  • Nonexistent workflow returned an empty result and actionable guidance (~0.1s).
  • Successful-run audit matched logs metadata and included job/step timing, resource metrics, MCP/tool usage, safe-output summary, and network counts (~5.7s). Parent success did not establish error-free tool execution: grader results reported tool failures.
  • Failed-run audit returned failure metadata matching logs and an actionable incomplete-task finding (~13.3s). Full report review was limited by output truncation.
  • Exactly three strict dry-run compile attempts: weekly-editors-health-check passed (~2.1s); windows failed its gate (~2.4s); archie was rejected (~1.2s). Two emitted locks were inspected for metadata, jobs, triggers, and safe-output jobs. No lock was executed or published.
Blocked or unfinished required checks

archie was rejected at .github/workflows/archie.md:1:1 because dry-run cannot safely process its pre-agent steps and custom MCP servers. No retry, fixture edit, or bypass was attempted. Thus three passing compile gates and full lock verification were not achieved. Audit report completeness beyond the visible bounded output remains unverified. A separate incomplete signal records these limits.

Not tested (expected exclusion)
  • Synthetic malformed YAML, invalid tool configurations, and missing imports: trusted-target restriction.
  • Private raw logs and independent artifact completeness: outside session scope.
  • Newly compiled lock execution: explicitly prohibited.
  • Additional historical/in-progress audits: bounded two-run sample.
  • Redundant date variants, future/old-date queries, invalid-ID audit, incremental compile repetition, and resource profiling: optional variants omitted to keep the sample bounded.
Next actions

Migrate the windows workflow key to report-missing-tool through the normal maintenance path and revalidate. Preserve the archie safety rejection. Existing-run evidence for weekly-editors-health-check comes from SHA cf88bbcb56e5844b95101d742daf79067dfb1300, not the newly emitted dry-run lock. No repository-wide health claim is made.

References:

Generated by 🧪 Daily Cli Tools Tester · codex · gpt60 · ~103 AIC · ⌖ ~62 AIC · ⊞ 21.3K · ◷

  • expires on Nov 12, 2026, 9:23 PM UTC-08:00
Lingua principale
Go
Stelle
5.6k
Fork
615
Merge medio
5h 21m
PR unite (30g)
792

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/gh-aw

Tutte le issue di github/gh-aw

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.