Skip to content

WIP debugging for busy copy#1658

Draft
KaiPrince wants to merge 36 commits intoProjectEvergreen:masterfrom
KaiPrince:kprince/diagnose-copy-busy
Draft

WIP debugging for busy copy#1658
KaiPrince wants to merge 36 commits intoProjectEvergreen:masterfrom
KaiPrince:kprince/diagnose-copy-busy

Conversation

@KaiPrince
Copy link
Copy Markdown
Contributor

Ignore this I'm trying to debug #1585 in ci

@KaiPrince
Copy link
Copy Markdown
Contributor Author

KaiPrince commented Mar 15, 2026

Having trouble reproducing the win loaders build 22 busy copy failure. All I've really changed is add a second test, but now they're both passing consistently.

All I know so far is the busy error is coming from the runner.runCommand('build') call. I suspect the copy of the setup is not finished and flushed before the build starts executing, but I haven't been able to determine conclusively.

(btw the netlify failures are not part of the fix attempt, only the windows loader build 22 matters here)

@KaiPrince
Copy link
Copy Markdown
Contributor Author

Also I tried a couple things to make CI faster, but wasn't able to make any noticeable speed improvements:

  • ci caching (4 min install -> 2 min restore + 2 min install)
  • yarn upgrade to v4 (got mismatched versions error in GitHub ci, suspect poor GHA support)
  • switch to bun (was not able to execute tests successfully)

run: |
yarn test:loaders:win
- name: Test fixed
if: ${{ always() }}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interesting, I'm not familiar with always(), what is it / does it do?

"author": "Owen Buckley <owen@thegreenhouse.io>",
"license": "MIT",
"type": "module",
"packageManager": "yarn@1.22.22",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fwiw, I would be open to this as a standalone PR 👍

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