Skip to content
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

Open
wants to merge 14 commits into
base: master
Choose a base branch
from
Open

Bump Playwright to 1.49.0 #44527

wants to merge 14 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 24, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@playwright/test (source) 1.48.2 -> 1.49.0 age adoption passing confidence
playwright (source) ^1.48.2 -> ^1.49.0 age adoption passing confidence
playwright (source) 1.48.2 -> 1.49.0 age adoption passing confidence

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Update of dependencies label Nov 24, 2024
@mui-bot
Copy link

mui-bot commented Nov 24, 2024

Netlify deploy preview

https://deploy-preview-44527--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 3f397e6

Copy link
Contributor Author

renovate bot commented Nov 25, 2024

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged label Nov 25, 2024
@github-actions github-actions bot added PR: out-of-date The pull request has merge conflicts and can't be merged and removed PR: out-of-date The pull request has merge conflicts and can't be merged labels Nov 25, 2024
@renovate renovate bot force-pushed the renovate/playwright branch from 126c08c to 5c987c5 Compare November 25, 2024 11:07
@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged label Nov 25, 2024
@renovate renovate bot force-pushed the renovate/playwright branch from 5c987c5 to dc94959 Compare November 25, 2024 11:35
@aarongarciah aarongarciah requested a review from a team November 25, 2024 13:07
@aarongarciah
Copy link
Member

@mui/code-infra Renovate didn't update the Docker image version in .circleci/config.yml as it did in previous Playwright bumps https://github.com/mui/material-ui/pull/44222/files#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R383

@JCQuintas
Copy link
Member

@mui/code-infra Renovate didn't update the Docker image version in .circleci/config.yml as it did in previous Playwright bumps https://github.com/mui/material-ui/pull/44222/files#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R383

It can't update images because new versions don't use ubuntu focal anymore. Gotta move them to noble

@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged label Nov 25, 2024
@renovate renovate bot force-pushed the renovate/playwright branch from 9eebeb6 to 365c0af Compare November 25, 2024 13:39
@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged label Nov 25, 2024
@aarongarciah
Copy link
Member

After manually pointing Playwright Docker images to playwright:v1.49.0-noble, the test_regression check fails: ReferenceError: __dirname is not defined

https://app.circleci.com/pipelines/github/mui/material-ui/143497/workflows/ca1efb19-79a9-4523-9b6a-9010a8de2c37/jobs/772782

@michaldudak
Copy link
Member

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).

See https://github.com/mui/base-ui/pull/836/files#diff-a00cb0d81882c4a00f2935b720a1e611c08e123551be2103da06c7022cd35ae7

@aarongarciah
Copy link
Member

aarongarciah commented Nov 27, 2024

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.

@JCQuintas
Copy link
Member

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).

See https://github.com/mui/base-ui/pull/836/files#diff-a00cb0d81882c4a00f2935b720a1e611c08e123551be2103da06c7022cd35ae7

This is odd, we didn't have this issue. mui/mui-x#15493

@JCQuintas
Copy link
Member

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.

Our argos changed a lot as well

Comment on lines +1 to +3
const path = require('path');
const fse = require('fs-extra');
const playwright = require('playwright');
Copy link
Member

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

Copy link
Member

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

Copy link
Member

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.

Copy link
Member

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.

Copy link
Member

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?

Copy link
Member

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.

@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged label Nov 27, 2024
@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged label Jan 22, 2025
@ZeeshanTamboli
Copy link
Member

@mui/code-infra There are many Argos changes. Should we consider this update?

@LukasTy
Copy link
Member

LukasTy commented Jan 23, 2025

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. 🤔
I don't see a problem bumping this dependency If all issues are the same. 😉

Nitpick: With mui/mui-x#9413 we have refactored the usage of playwright to rely only on the @playwright/test package.

@ZeeshanTamboli
Copy link
Member

Nitpick: With mui/mui-x#9413 we have refactored the usage of playwright to rely only on the @playwright/test package.

I can do this in a separate PR. Thanks for pointing.

@Janpot
Copy link
Member

Janpot commented Jan 23, 2025

Those issues look like font aliasing problems that a browser version update could easily cause.

It's caused by the ubuntu update

Screenshot 2025-01-23 at 09 32 08

vs.

Screenshot 2025-01-23 at 09 32 02

looks a lot like https://askubuntu.com/questions/1511954/font-rendering-issue-antialiasing

@LukasTy
Copy link
Member

LukasTy commented Jan 23, 2025

It's caused by the ubuntu update

Thanks for clarifying. 👍
Regardless, I think we can accept such changes, unless we want to maintain the current behavior and install additional fonts on every CI. 🙈
P.S. We also had the same case on mui/mui-x#15493 (https://app.argos-ci.com/mui/mui-x/builds/27489/122799699).

@Janpot
Copy link
Member

Janpot commented Jan 23, 2025

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)

@LukasTy
Copy link
Member

LukasTy commented Jan 23, 2025

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 have done exactly that for mui-x PR and found at least one problem, however, in that case, we had explicit changes in some testing code. 😉

@ZeeshanTamboli
Copy link
Member

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.

@Janpot
Copy link
Member

Janpot commented Jan 23, 2025

I don’t see any above changes in the deploy preview of this PR

Same, this looks like a bug in argos. Looks like their screenshots don't line up correctly when calculating the diff. Can't find a ticket for it though.

Screenshot 2025-01-23 at 10 20 16

@ZeeshanTamboli
Copy link
Member

I think we should proceed with accepting the changes.

@LukasTy
Copy link
Member

LukasTy commented Jan 23, 2025

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. 👍 🎉

@ZeeshanTamboli
Copy link
Member

I approved the Argos changes. Can someone review the file changes and approve if they look good?

Copy link
Member

@LukasTy LukasTy left a 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.

Comment on lines +1 to +3
const path = require('path');
const fse = require('fs-extra');
const playwright = require('playwright');
Copy link
Member

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?

@Janpot
Copy link
Member

Janpot commented Jan 23, 2025

Yeah, moving from ESM to commonjs is a regression. I'd prefer it if we either motivate it well or fix it.

@ZeeshanTamboli
Copy link
Member

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?

@Janpot
Copy link
Member

Janpot commented Jan 24, 2025

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?

@ZeeshanTamboli
Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Update of dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants