-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[support/4.x] Backport: GitHub Actions + Jest fixes for Windows #4006
Conversation
f8a74d0
to
afc81a9
Compare
63afd26
to
a68403e
Compare
afc81a9
to
c49196d
Compare
We see failures due to Express.js startup delays, awaiting selector visibility, and accessibility tests taking 60+ seconds to loop through all component examples (cherry picked from commit 6106aa0)
Required for `workflow_call` calls but still works with `workflow_dispatch` (cherry picked from commit d2fdf07)
We previously let these Jest projects run early: 1. JavaScript unit tests 2. Nunjucks macro tests But they both finish sooner than the “Accessibility tests” project (cherry picked from commit 6ef1864)
a68403e
to
02d498d
Compare
c49196d
to
7c85d71
Compare
(cherry picked from commit 00dcfd9)
All the cache keys have also been changed to ensure all archives are recreated (cherry picked from commit ea9eb03)
Unlike on Linux, tests run slower when concurrent due to the number of open Chrome windows/tabs (cherry picked from commit 87e4b2c)
We already skip package tests as we have coverage in our PR tests already (cherry picked from commit 02f1c68)
7c85d71
to
f4c451c
Compare
The only thing I'm not 100% sure about is pinning to exact GitHub versions… Dependabot will (as currently configured) only raise PRs to bump GitHub Action workflows on the Equally that might be desired – it's unlikely there'll be much activity on this branch post v5, but we want to keep it releasable. So pinning to specific versions might actually help with that. Thoughts? |
Equally, pinning leaves us vulnerable to uncaught security warnings when I think it probably makes sense to pin everything, then configure security bumps for the branch? Security fixes are pretty much what we're committing to anyway. |
Great minds! I had the exact same thoughts but kept it solely for stability For example, when releasing v4.8.0 we know what worked 3 months ago still works now, avoiding any surprise GitHub Action updates that slipped in a breaking change whilst we were busy on v5 Could look into Dependabot |
Sorry @domoscargin I missed your reply whilst typing |
Unfortunately, as far as I can tell, Dependabot doesn't support security updates against multiple branches 😞 |
f4c451c
to
012c3e6
Compare
So we can discuss further + unblock, I've split out the commits that pin GitHub Actions versions: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Backport looks fine, let's merge it ⛵
Partially backports #3816 and #3863 for v4.x for Windows test reliability
Note: Changes related to path handling #3756 (v5 only) were excluded