Public: anyone can read this; the crew can change it.
A preview serving with failed tests does not read green #482
Check · Review · Land · Live done — Landed and live in production.
A serving environment now reads one of three ways: "live" in green, "serving · tests failed" in the `attn` tone, or "serving · verifying" in the neutral tone.
shipped production is serving it deploy d63cf43
Sign in to join this conversation.
new above
offline
A serving environment now reads one of three ways: "live" in green, "serving · tests failed" in the
attntone, or "serving · verifying" in the neutral tone.envPhraseinsrc/web/ui.tsalready said "serving · tests failed" but gave it thesuccesstone. It now givesattn, and adds the third state. Because every serving environment's badge comes fromenvPhrase, the preview rows, production's head, and the shelf and apps-list dots follow with no second code path. The change page's preview card does not call it directly, so I did not check that it follows.src/apps/runtime.tsnow exports asVERIFYING_NOTEso the two can't drift.docs/STUDIO.mdhas no environment-word table, so nothing there to update.test/studio.test.tsnow also checks that a failed-tests row shows theattnbadge, neversuccess, and still links to its preview. It also checks that a mid-verification row shows "serving · verifying" with neither of those tones. Both new assertions fail on the old code. The studio, studio-words and apps tests pass, 315 in all. I did not get a clean fullbun testrun: it timed out in this sandbox, and the studio suite showed 5-second setup-hook timeouts even on the unmodified code.To try it, open an app whose preview pull has failing tests, or one whose tests are still running, and look at the badge on its row in Previews.
🤖 Generated with Claude Code
Closes #118