[smoke-otel-tracing] OTEL smoke: jest flag silently skipped, diagnostic path mismatch, api-proxy spans unverified

Abierto
#11,800 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, typescript

Línea de trabajo

Start with .github/workflows/smoke-otel-tracing.md and its compiled .lock.yml; compare the Jest command and diagnostic log paths, then trace the api-proxy log host mapping from containers/api-proxy/otel.js. The issue reports that --testPathPatterns passes 75 tests. Confirm the mapping and span output in the post-step; done when the workflow fails on Jest errors, reads the correct log, and verifies api-proxy spans and token attributes.

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

Descripción

automation otel smoke-test tracing

Smoke run 44409831996 (PR #11794) found three defects in .github/workflows/smoke-otel-tracing.md and its compiled .lock.yml.

1. Test step never runs tests (unexpected failure)

The "Run api-proxy OTEL tests" step runs npx jest --verbose --ci --testPathPattern='otel' 2>&1 || true. The installed Jest (30.1.3) rejects --testPathPattern with Option "testPathPattern" was replaced by "--testPathPatterns" and exits 1. The || true hides this, so the step reports success with no tests run.

Running npx jest --ci --testPathPatterns='otel' in containers/api-proxy passes: 3 suites, 75/75 tests (otel.test.js, otel-fanout.test.js, otel-workload-identity.test.js).

Fix: use --testPathPatterns in both the .md and .lock.yml, and remove || true so a failing invocation fails the step.

2. Diagnostic path mismatch
  • smoke-otel-tracing.md post-step reads /tmp/gh-aw/sandbox/firewall/logs/api-proxy/otel.jsonl.
  • The compiled .lock.yml reads /tmp/gh-aw/sandbox/firewall/logs/api-proxy-logs/otel.jsonl.

The api-proxy writes /var/log/api-proxy/otel.jsonl inside the container (containers/api-proxy/otel.js). Confirm the host mapping, fix the source, and recompile.

3. api-proxy span export not verified

At agent time, /tmp/gh-aw/sandbox/firewall/logs was empty. The only exported span was gh-aw.agent.setup (in /tmp/gh-aw/otel.jsonl), not an api-proxy request span, so no gen_ai.usage.* attributes were observed. The post-step runs after the agent, so confirm span export and token attributes in that step's output for this run.

Passing scenarios
  • otel.js loads; isEnabled() returns true; exports include startRequestSpan, setTokenAttributes, endSpan, endSpanError, shutdown.
  • Env forwarding: GITHUB_AW_OTEL_TRACE_ID and GITHUB_AW_OTEL_PARENT_SPAN_ID in env-passthrough.ts; GH_AW_OTLP_ENDPOINTS, OTEL_EXPORTER_OTLP_ENDPOINT, and both trace IDs in api-proxy-env-config.ts.
  • onUsage hook present in containers/api-proxy/token-tracker-http.js.

📡 OTel tracing validated by Smoke OTel Tracing
Add label ready-for-aw to run again

  • expires on Nov 25, 2026, 10:37 PM UTC
Lenguaje dominante
TypeScript
Estrellas
165
Forks
84
Merge medio
5 h 57 min
PR fusionados (30 d)
390

Preparar el entorno

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-firewall

Todos los issues de github/gh-aw-firewall

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.