Skip to content

Smoke test polish: krater show marks it, no false upload failure in the log - #79

Merged
Adambomb210 merged 1 commit into
mainfrom
claude/smoke-polish
Nov 13, 2026
Merged

Adambomb210 merged 1 commit into
mainfrom
claude/smoke-polish

Conversation

@Adambomb210

Copy link
Copy Markdown
Collaborator

Two small gaps the first paid staging smoke test turned up (job c7da2d0d, after #77):

  • krater show didn't say a job is a smoke test (krater jobs did). It now prints
    smoke test: the command is stopped after N minutes of running, and once the job has passed it adds
    `krater rerun <id> --no-smoke` queues the full run.
  • The runner logged a false failure. The command's end cancels the periodic sync loops. A log upload in
    flight at that moment logged uploading attempt-1.log failed: ... context canceled, though the final push
    then saved the whole log. A 1-minute smoke test hit this every time, because its timer lands on the 60 s
    log-sync tick. Syncer.Push and pushWorkspace no longer log a per-file failure when their context was
    cancelled. The error is still returned, and syncLoop already ignored it.

Tests: go vet and go test -race ./... pass (new TestACancelledPushDoesNotLogAFailedUpload), and the
CLI suite passes 192 tests (new test_show_says_a_job_is_a_smoke_test). Ruff and gofmt are clean.

No migration. The runner change ships with the portal image.

🤖 Generated with Claude Code

…he log

- `krater show` says a job is a smoke test, and once it has passed gives the
  `krater rerun <id> --no-smoke` line (`krater jobs` already marked it).
- The runner no longer logs "uploading X failed: context canceled" when the
  command's end cancels a periodic sync mid-upload. The final push uploads the
  file again, so it wasn't a failure; a 1-minute smoke test hit it every time,
  since its timer lands on the 60 s log sync tick.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Adambomb210
Adambomb210 merged commit e36b395 into main Nov 13, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant