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

chore(test): revert pw framework update #1277

Merged
merged 6 commits into from
Feb 6, 2025
Merged

Conversation

cbr7
Copy link
Contributor

@cbr7 cbr7 commented Feb 5, 2025

What does this PR do?

Tries to failing e2e tests that started not working 2 days ago.

What issues does this PR fix or reference?

#1278

@cbr7 cbr7 marked this pull request as ready for review February 5, 2025 10:19
@cbr7 cbr7 requested a review from a team as a code owner February 5, 2025 10:19
@cbr7 cbr7 requested review from benoitf, feloy and axel7083 and removed request for a team February 5, 2025 10:19
@cbr7 cbr7 linked an issue Feb 5, 2025 that may be closed by this pull request
@cbr7 cbr7 requested review from deboer-tim and odockal February 5, 2025 10:22
@cbr7
Copy link
Contributor Author

cbr7 commented Feb 5, 2025

@deboer-tim looks like dependobot updated the PW framework to version 1.15.1 two days ago, at which point the e2e tests started failing, I'm not sure what is causing the failures, since the update seems to be working fine elsewhere, but in the meantime I made this PR to revert the update and get the tests running while we investigate.

@cbr7
Copy link
Contributor Author

cbr7 commented Feb 5, 2025

PR check seems to be passing now but running e2e tests on windows still has the same issue, so I don't think this PR fixed whatever problem there is, at least not completely.

Copy link
Contributor

@deboer-tim deboer-tim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's up to you guys. I'm ok reverting if it gives more chance to investigate.

In general I'd prefer moving to a place where e2e tests must pass and are testing only the current branch. Nightly wouldn't work for that either (since it's testing the previous one, or could fail if we're fixing a previous release like 1.6.1?), but again, it's better than before and could improve later.

@cbr7
Copy link
Contributor Author

cbr7 commented Feb 5, 2025

@deboer-tim the pr check does run on current branch, it builds it locally and installs it, PR check does not use the nightly build.

cbr7 and others added 2 commits February 6, 2025 09:26
@cbr7 cbr7 merged commit 4319de2 into podman-desktop:main Feb 6, 2025
6 checks passed
@cbr7 cbr7 deleted the deps_changes branch February 6, 2025 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

e2e tests are failing on main currently
2 participants