test: run-process --trace subprocess flakes with "Model not found: test/test-model" while sibling tests pass

Open
#1,340 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, testing

Research direction

Start with test/cli/run/run-process.test.ts and the --trace subprocess test, then inspect expectExit and the test provider setup. Reproduce the failure under the bounded subprocess suite or load conditions, and compare it with the four sibling tests. Done means the test no longer flakes with “Model not found: test/test-model” while preserving the existing exit and trace assertions.

Written by the indexing model from the issue text.

Description

Flake

test/cli/run/run-process.test.ts › "opencode run (non-interactive subprocess) > --trace writes a session trace artifact" failed once on the v0.12.1 release PR (#1338, head a2ff011130) with no related code change:

[opencode] expected exit 0, got 1 after 3075ms
Error: Model not found: test/test-model
Try: `altimate models` to list available models

The four sibling subprocess tests in the same file — same test provider, same model — passed in the same run seconds earlier, and the same test passed on the PR's previous heads. The branch touches nothing under cli/cmd/run, tracing, or provider config. Run: https://github.com/AltimateAI/altimate-code/actions/runs/35602891038

Looks like the subprocess occasionally starts before the test provider registration is visible to it (config read race), or the bounded subprocess suite is scheduling-sensitive under load. Worth a bounded retry inside expectExit for this shape, or a readiness check on the test provider before spawning.

Filed so the re-run has a paper trail per the release process.

🤖 Generated with Claude Code

https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE6

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.