[Bug]: some actions do not appear in the trace file #31764
Assignees
Labels
Comments
|
this bug seems to have been introduced in 1.45.0. as far as i can tell it appears that actions with the same function name as a previous action are overwriting the previous one |
dgozman
added a commit
that referenced
this issue
Jul 19, 2024
Without `wallTime`, actions are matched by `actionName:undefined` and all actions with the same are merged. Fixes #31764.
yury-s
pushed a commit
to yury-s/playwright
that referenced
this issue
Jul 20, 2024
…hould not merge actions Without `wallTime`, actions are matched by `actionName:undefined` and all actions with the same are merged. Fixes microsoft#31764.
yury-s
pushed a commit
to yury-s/playwright
that referenced
this issue
Jul 22, 2024
…hould not merge actions Without `wallTime`, actions are matched by `actionName:undefined` and all actions with the same are merged. Fixes microsoft#31764.
szinn
referenced
this issue
in szinn/wordacle
Jul 23, 2024
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@playwright/test](https://playwright.dev) ([source](https://togithub.com/microsoft/playwright)) | devDependencies | patch | [`1.45.2` -> `1.45.3`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.45.2/1.45.3) | --- ### Release Notes <details> <summary>microsoft/playwright (@​playwright/test)</summary> ### [`v1.45.3`](https://togithub.com/microsoft/playwright/releases/tag/v1.45.3) [Compare Source](https://togithub.com/microsoft/playwright/compare/v1.45.2...v1.45.3) ##### Highlights [https://github.com/microsoft/playwright/issues/31764](https://togithub.com/microsoft/playwright/issues/31764) - \[Bug]: some actions do not appear in the trace file[https://github.com/microsoft/playwright-java/issues/1617](https://togithub.com/microsoft/playwright-java/issues/1617)7 - \[Bug]: Traceviewer not reporting all actions #### Browser Versions - Chromium 127.0.6533.5 - Mozilla Firefox 127.0 - WebKit 17.4 This version was also tested against the following stable channels: - Google Chrome 126 - Microsoft Edge 126 </details> <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQ0MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL3BhdGNoIl19--> Co-authored-by: repo-jeeves[bot] <106431701+repo-jeeves[bot]@users.noreply.github.com>
This was referenced Aug 12, 2024
This was referenced Aug 12, 2024
This was referenced Aug 13, 2024
This was referenced Aug 16, 2024
Open
Open
Open
Open
This was referenced Aug 22, 2024
Open
Open
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.2
Steps to reproduce
npm cinode index.jsplaywright show-trace asdf.zipExpected behavior
all four locator actions appear in the trace file
Actual behavior
only the last 2 actions appear:
Additional context
No response
Environment
System: OS: Windows 11 10.0.22621 CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11500H @ 2.90GHz Memory: 9.70 GB / 31.20 GB Binaries: Node: 19.7.0 - ~\AppData\Roaming\node\node.EXE npm: 9.5.0 - ~\AppData\Roaming\node\npm.CMD IDEs: VSCode: 1.91.1 - C:\Users\user\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD npmPackages: playwright: ^1.45.2 => 1.45.2The text was updated successfully, but these errors were encountered: