Skip to content

fix: add mc binary to PATH in e2e CI job#58

Merged
DarlingtonDeveloper merged 1 commit into
mainfrom
fix/ci-e2e-path
Feb 15, 2026
Merged

fix: add mc binary to PATH in e2e CI job#58
DarlingtonDeveloper merged 1 commit into
mainfrom
fix/ci-e2e-path

Conversation

@DarlingtonDeveloper
Copy link
Copy Markdown
Collaborator

Summary

  • The e2e job builds mc to $GITHUB_WORKSPACE/bin/mc but never adds that directory to $PATH
  • When the orchestrator shells out to mc task create during POST /api/tasks, exec.Command can't find the binary, returning a 500
  • Adds a $GITHUB_PATH step so mc is available for the entire e2e job

Root cause

handleCreateTask in orchestrator/api/handlers.go calls s.runMC("task", "create", ...) which uses exec.Command("mc", ...). The binary exists at $GITHUB_WORKSPACE/bin/mc but that's not on $PATH.

Test plan

  • CI e2e job passes — POST /api/tasks should return 201 instead of 500
  • All other e2e tests continue to pass

🤖 Generated with Claude Code

The e2e job builds `mc` to `$GITHUB_WORKSPACE/bin/mc` but never adds
that directory to `$PATH`. When the orchestrator server shells out to
`mc task create` during POST /api/tasks, exec.Command cannot find the
binary, causing a 500 error.

Uses `$GITHUB_PATH` to make the binary available for the full job.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@DarlingtonDeveloper DarlingtonDeveloper merged commit 803ee20 into main Feb 15, 2026
3 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