-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Bug]: missing trace for 2nd browser #31601
Labels
Comments
Looks like already fixed on ToT - @dgozman should we cherry-pick? |
hmm, there were case which sounds exactly like this , but looks like that tests didn't found ( one more ) regression :( |
I can verify this is fixed on @beta and should be fixed in v1.45.2 shortly. |
This was referenced Aug 6, 2024
This was referenced Aug 12, 2024
This was referenced Aug 12, 2024
This was referenced Aug 13, 2024
This was referenced Sep 24, 2024
Open
Open
This was referenced Sep 26, 2024
This was referenced Sep 27, 2024
Open
Open
Open
Open
Open
Open
This was referenced Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
1.45.1
Steps to reproduce
Expected behavior
Actual behavior
Additional context
1.44.1 was fine, 1.45.1 - fails
Environment
System: OS: macOS 14.5 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 20.10 MB / 32.00 GB Binaries: Node: 20.13.1 - /usr/local/bin/node npm: 10.5.2 - /usr/local/bin/npm pnpm: 9.4.0 - /usr/local/bin/pnpm Languages: Bash: 3.2.57 - /bin/bash npmPackages: @playwright/test: 1.45.1 => 1.45.1
The text was updated successfully, but these errors were encountered: