Skip to content

Fix yarn.lock stale dependency causing benchmark workflow failure#63

Draft
Copilot wants to merge 2 commits into
masterfrom
copilot/update-action-job-configuration
Draft

Fix yarn.lock stale dependency causing benchmark workflow failure#63
Copilot wants to merge 2 commits into
masterfrom
copilot/update-action-job-configuration

Conversation

Copilot AI commented Jan 10, 2026

Copy link
Copy Markdown

The benchmark workflow failed due to a lockfile mismatch. The yarn.lock contained @aglocal/benchmark: workspace:* as a dependency of @aglocal/boot, but this dependency was absent from packages/boot/package.json.

Root Cause

The run-bench.js script executes benchmarks via direct file path using execFileSync:

const BENCHMARK_SCRIPT = join(
  __dirname,
  '..',
  'benchmark',
  'benchmark',
  'benchmark-stress-vaults.js',
);

execFileSync('node', [BENCHMARK_SCRIPT, ...]);

No module dependency on @aglocal/benchmark is needed.

Changes

  • Removed stale "@aglocal/benchmark": "workspace:*" entry from @aglocal/boot dependencies in yarn.lock
  • Removed duplicate workspace:* variant from @aglocal/benchmark package descriptor

The lockfile now matches the package.json state, allowing yarn install --immutable to pass in CI.

Original prompt

Reference: https://github.com/Snapp949/agoric-sdk/actions/runs/20874564653/job/59981969357


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

The lockfile contained a stale dependency reference to @aglocal/benchmark from @aglocal/boot that was no longer in package.json. This caused the benchmark workflow to fail with a lockfile mismatch error.

Co-authored-by: Snapp949 <173113150+Snapp949@users.noreply.github.com>
Copilot AI changed the title [WIP] Update action job configuration for enhanced performance Fix yarn.lock stale dependency causing benchmark workflow failure Jan 10, 2026
Copilot AI requested a review from Snapp949 January 10, 2026 07:12
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.

2 participants