Since the recent changes applied a cache to ci workflows, npm ci is not run when the cache is restored, which in turn implies that the postinstall script won't be invoked. The postinstall script, however, triggered npx playwright install, which installed playwright's browsers binaries to ~/.cache/ms-playwright.
What would fix the problem would either be running this manually if the cache was restored instead of npm ci having been run, or to cache ~/.cache/ms-playwright.
As others have already encountered this problem as well and noticed here that download times are very fast, this PR introduces the first approach: to run npm run postinstall manuall, which is also more scalable since this will always download the newest supported browser binaries; for speed-up, this step is only added to ci.yml, but not to cd.yml (which does not need neither playwright, nor lefthook).
Linked issues (if any)
N/A
Checklist before requesting a review
[x] E2E tests' snapshots (screenshots) are up-to-date
Describe your changes
Since the recent changes applied a cache to ci workflows,
npm ciis not run when the cache is restored, which in turn implies that thepostinstallscript won't be invoked. Thepostinstallscript, however, triggerednpx playwright install, which installed playwright's browsers binaries to~/.cache/ms-playwright. What would fix the problem would either be running this manually if the cache was restored instead ofnpm cihaving been run, or to cache~/.cache/ms-playwright.As others have already encountered this problem as well and noticed here that download times are very fast, this PR introduces the first approach: to run
npm run postinstallmanuall, which is also more scalable since this will always download the newest supported browser binaries; for speed-up, this step is only added toci.yml, but not tocd.yml(which does not need neither playwright, nor lefthook).Linked issues (if any)
N/A
Checklist before requesting a review