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

fix(tracing): support old traces with consoleMessage.args #27095

Merged
merged 1 commit into from
Sep 15, 2023

Conversation

dgozman
Copy link
Contributor

@dgozman dgozman commented Sep 14, 2023

Fixes #27072.

@github-actions
Copy link
Contributor

Test results for "tests 1"

1 failed
❌ [playwright-test] › test-step.spec.ts:1090:5 › should show final toPass error

4 flaky ⚠️ [chromium] › library/tracing.spec.ts:239:5 › should not include trace resources from the previous chunks
⚠️ [chromium] › page/page-event-request.spec.ts:130:3 › should report navigation requests and responses handled by service worker with routing
⚠️ [webkit] › library/browsercontext-reuse.spec.ts:50:1 › should reset serviceworker
⚠️ [webkit] › library/inspector/cli-codegen-pytest.spec.ts:56:5 › should save the codegen output to a file if specified

25651 passed, 606 skipped
✔️✔️✔️

Merge workflow run.

@dgozman dgozman merged commit a26f568 into microsoft:main Sep 15, 2023
27 of 28 checks passed
dgozman added a commit to dgozman/playwright that referenced this pull request Sep 15, 2023
dgozman added a commit that referenced this pull request Sep 15, 2023
dgozman added a commit that referenced this pull request Sep 19, 2023
…essage.args (#27162)

This moves the fix in #27095 from `modernize` to `appendEvent`. The
reason is that `trace V4` is used both for older traces that do not have
`consoleMessage.args` and the new ones with `args`. Since we do not call
`modernize` for traces of the same version, the original fix does not
help in this case.

Fixes #27144.
dgozman added a commit to dgozman/playwright that referenced this pull request Sep 19, 2023
… migrate V4 traces to consoleMessage.args

This moves the fix in microsoft#27095 from `modernize` to `appendEvent`. The
reason is that `trace V4` is used both for older traces that do not have
`consoleMessage.args` and the new ones with `args`. Since we do not call
`modernize` for traces of the same version, the original fix does not
help in this case.

Fixes microsoft#27144.
dgozman added a commit that referenced this pull request Sep 20, 2023
…V4 traces to consoleMessage.args (#27193)

This moves the fix in #27095 from `modernize` to `appendEvent`. The
reason is that `trace V4` is used both for older traces that do not have
`consoleMessage.args` and the new ones with `args`. Since we do not call
`modernize` for traces of the same version, the original fix does not
help in this case.

Fixes #27144.
Germandrummer92 pushed a commit to OctoMind-dev/playwright that referenced this pull request Oct 27, 2023
Germandrummer92 pushed a commit to OctoMind-dev/playwright that referenced this pull request Oct 27, 2023
…essage.args (microsoft#27162)

This moves the fix in microsoft#27095 from `modernize` to `appendEvent`. The
reason is that `trace V4` is used both for older traces that do not have
`consoleMessage.args` and the new ones with `args`. Since we do not call
`modernize` for traces of the same version, the original fix does not
help in this case.

Fixes microsoft#27144.
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.

[BUG] PWT trace viewer fails to load trace and throws TypeError
2 participants