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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#75,317 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, go
Área
ci-cd, tooling

Línea de trabajo

Empieza por la configuración del workflow windows y localiza su clave de salida segura obsoleta missing-tool; el issue identifica report-missing-tool como reemplazo. Actualiza la clave mediante el proceso normal de mantenimiento, vuelve a ejecutar la compilación estricta en modo dry-run para windows y confirma que tanto el resultado del workflow como la verificación del lote se superan.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Go
Estrellas
5.6k
Forks
615
Merge medio
5 h 21 min
PR fusionados (30 d)
792

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/gh-aw

Todos los issues de github/gh-aw

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.