-
-
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
Bump Playwright to 1.49.0 #44527
base: master
Are you sure you want to change the base?
Bump Playwright to 1.49.0 #44527
Conversation
Netlify deploy previewhttps://deploy-preview-44527--material-ui.netlify.app/ Bundle size report |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
cf21bbf
to
126c08c
Compare
126c08c
to
5c987c5
Compare
5c987c5
to
dc94959
Compare
@mui/code-infra Renovate didn't update the Docker image version in |
It can't update images because new versions don't use ubuntu focal anymore. Gotta move them to |
9eebeb6
to
365c0af
Compare
After manually pointing Playwright Docker images to |
We had the same issue in Base UI. For some reason, the main test file has to be proper CommonJS or ESM, not a blend of both (which is actually a good thing). |
Thanks @michaldudak. It now works after applying that change. @mui/code-infra this is ready for review. There's a lot of changed screenshots in Argos (946), most of them probably caused by the Chromium version update (129 -> 131) causing minor differences in text rendering. |
This is odd, we didn't have this issue. mui/mui-x#15493 |
Our argos changed a lot as well |
const path = require('path'); | ||
const fse = require('fs-extra'); | ||
const playwright = require('playwright'); |
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 believe the issue is that you are using @mui/internal-test-utils/setupBabelPlaywright
inside test/regressions/.mocharc.js
instead of @mui/internal-test-utils/setupBabel
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.
The playwright specific config seems unnecessary to me btw, maybe we should remove it @michaldudak
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.
Changing this to setupBabel
causes the tests in Base UI to explode, so it may require a bit more work. I'd love to get rid of webpack and mocha and replace them with vite and vitest at some point.
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.
Ah, but this seems to work in core. I'm still having trouble with vitest on X, but the next step would be to try to use the same tools everywhere indeed.
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.
Is this still a problem?
Are these changes needed?
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.
Yes. I tried removing it and going back to import
but it doesn't work.
@mui/code-infra There are many Argos changes. Should we consider this update? |
Those issues look like font aliasing problems that a browser version update could easily cause. 🤔 Nitpick: With mui/mui-x#9413 we have refactored the usage of |
I can do this in a separate PR. Thanks for pointing. |
It's caused by the ubuntu update vs. looks a lot like https://askubuntu.com/questions/1511954/font-rendering-issue-antialiasing |
Thanks for clarifying. 👍 |
Yes, we can accept them, I don't think it matters much, we can't control our user's systems neither. My only worry is, how do we know there are no other issues in this update? Ideally we go through all of the changed screenshots to verify the only changes are in font aliasing. It should be fairly quick to do with the red changes overlay and the arrow keys, I've done it before 🙂. (I think we should never accept screenshot changes we haven't verified based on the assumption they are caused by one and the same thing) |
Oh yes, clearly that has to be done. 🙈 |
I checked everything but am unsure about these changes:
And several others like these. I don’t see any above changes in the deploy preview of this PR—maybe because I’m using Windows OS. The rest of the changes show red lines on fonts. |
I think we should proceed with accepting the changes. |
If you have looked through all the diffs and nothing "clearly" wrong jumped to you - go ahead. 👍 🎉 |
I approved the Argos changes. Can someone review the file changes and approve if they look good? |
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.
LGTM, besides the open question about the change of import type.
const path = require('path'); | ||
const fse = require('fs-extra'); | ||
const playwright = require('playwright'); |
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.
Is this still a problem?
Are these changes needed?
Yeah, moving from ESM to commonjs is a regression. I'd prefer it if we either motivate it well or fix it. |
So the next step I assume is to keep this PR on hold until we migrate to ESM? |
I would just want to know what's going on. How can, in 2024, an update to a package, force you to regress back to commonjs? Is it a bug in playwright? |
See conversation from #44527 (comment). Is it because we don't use ESM everywhere? |
This PR contains the following updates:
1.48.2
->1.49.0
^1.48.2
->^1.49.0
1.48.2
->1.49.0
Release Notes
microsoft/playwright (@playwright/test)
v1.49.0
Compare Source
Configuration
📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.