Drop docker_cmd for graymatter performance#37
Conversation
Mirrors #35 (which dropped docker_cmd from the graymatter fuzz job) for the performance job. The graymatter target rejects the legacy fuzz-m1-target CLI args and instead reads JAM_FUZZ_SOCK_PATH etc. from the standard target packaging env vars (added in #33). - graymatter-performance.yml: drop docker_cmd entirely. - reusable-picofuzz.yml: docker_cmd is now optional (default ""). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe ChangesWorkflow Configuration Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
docker_cmdfromgraymatter-performance.yml; the graymatter image rejects the legacyfuzz-m1-targetCLI args and readsJAM_FUZZ_SOCK_PATHetc. from env vars (added in Pass standard target packaging env vars to targets #33).docker_cmdoptional (default"") inreusable-picofuzz.yml, matching the change applied todemo-source.ymlin Drop docker_cmd for graymatter; rely on JAM_FUZZ_* env vars #35.Mirrors #35 for the performance job.
Test plan
Performance: graymatterworkflow run starts the target with no CLI args and completes minifuzz + picofuzz suites.docker_cmd) are unaffected.🤖 Generated with Claude Code
Summary by CodeRabbit