Open colinrotherham opened 7 months ago
Thanks for reporting this, I tried to
@prettier/sync
to v0.5.0 in packages/govuk-frontend-review/
yarn jest --color --coverage=false --maxWorkers=2 --selectProjects "Accessibility tests"
But I can't see any error. Did I do something wrong?
After cleaning .cache
and run tests on Node.js 20.9.0, still can't get an error.
Thanks @fisker
Looks like your PR + a few re-runs didn't get the error either today
If we take a look at the GitHub Actions runs that failed last week:
- https://github.com/alphagov/govuk-frontend/actions/runs/7698179202/job/20977038657
- https://github.com/alphagov/govuk-frontend/actions/runs/7697352994/job/20974366348
- https://github.com/alphagov/govuk-frontend/actions/runs/7696099803/job/20970540369
- https://github.com/alphagov/govuk-frontend/actions/runs/7695785158/job/20969630574
- https://github.com/alphagov/govuk-frontend/actions/runs/7707963406/job/21006202743
The npm package lines in make-synchronized/index.cjs
(compiled from threads-worker.js
) throw at:
try {
lock.lock(1e3);
} catch (error) {
if (error instanceof atomics_wait_timeout_error_default) {
throw new Error(
`Unexpected error, most likely caused by syntax error in '${WORKER_FILE}'`
);
}
throw error;
}
Perhaps on GitHub Actions, under some loads, we're seeing the 1000ms timeout is too slow?
Rather than syntax error
Removed that check in #25, you can try @prettier/sync v0.5.1. https://github.com/prettier/prettier-synchronized/releases/tag/v0.5.1
Since
@prettier/sync
introducedmake-synchronized
we've seen unexpected errors thrown on WindowsThis doesn't happen all the time and re-running build steps will temporarily resolve the issue
Hope this is helpful for others
Log output
Here's stack trace we've seen regularly but see more examples in https://github.com/alphagov/govuk-frontend/pull/4695