-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[code-infra] Remove custom playwright installation steps #43881
Conversation
Netlify deploy previewhttps://deploy-preview-43881--material-ui.netlify.app/ Bundle size report |
This reverts commit b86516d.
@@ -74,25 +73,15 @@ commands: | |||
steps: | |||
- run: | |||
name: Install pnpm package manager | |||
command: | | |||
corepack enable | |||
corepack prepare pnpm@latest-8 --activate |
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.
I suppose we dont need this anymore because we are defining it in the package.json?
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.
Yep, I don't even think it was ever needed.
Closes #43880
The caching currently is not working and fixing it decreases performance even more.
In fact it's not even necessary to install those browsers as we use the
mcr.microsoft.com/playwright:v1.47.1-focal
image which comes with the correct ones preinstalled, just have to remove the custom install location so playwright can find them instead of the ones we install after.We were basically:
This should reduce runtime of jobs that use a browser with ~40s
Also slightly cleaning up the corepack steps
To investigate next: is it possible to use the regular node image but with a playwright install step, and what would be the performance impact vs. using
mcr.microsoft.com/playwright:v1.47.1-focal
? See #43883