flake: TestSnapshotChanged_MultipleConfigFiles (multiple variants)
Nadie ha tomado este issue todavía.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
CI Run: https://github.com/coder/coder/actions/runs/29076046174
Job: test-go-pg (ubuntu-latest)
Failure time: 2026-07-10T07:28:11Z
Commit: 3d8ffd34b3054ca192c471b6aa9546d4d910741f (Thomas Kosiewski)
Failed tests:
- agent/x/agentmcp TestSnapshotChanged_MultipleConfigFiles (reload_internal_test.go:249)
- agent/x/agentmcp TestReload/SequentialReloadsDiffDetect (reload_internal_test.go:386)
Error evidence:
- TestSnapshotChanged_MultipleConfigFiles:
Error: Should be true/ message:snapshot should change when second file is mutated - TestReload/SequentialReloadsDiffDetect:
Error: Should be true
No panic/OOM indicators and no data race warnings observed in the job log excerpt.
Root cause assessment:
Likely flaky snapshot-change detection (file mutation not observed). Both failing assertions are SnapshotChanged returning false after rewriting .mcp.json, suggesting a timing/mtime/fsnotify edge where the second write isn’t picked up immediately.
Assignment analysis:
- git blame -L 240,270 agent/x/agentmcp/reload_internal_test.go
- git blame -L 370,395 agent/x/agentmcp/reload_internal_test.go
Both lines were last modified in 27ecd17991f54ae26a78941bdccd48ff3ab8185f (Kyle Carberry) “refactor: consolidate agent MCP onto a single persistent engine (#26599)”, which updated these tests to use the new connected catalog helpers.
Related issues:
- None found after searching coder/internal for TestSnapshotChanged_MultipleConfigFiles, SequentialReloadsDiffDetect, reload_internal_test.go, or "snapshot should change".
Reproduction:
- Not known; appears intermittent.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 3
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de coder/internal
-
flake
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
-
flake
-
flake
-
flake