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): bump trace version to V5, migrate V4 traces to consoleMessage.args #27162

Merged
merged 2 commits into from
Sep 19, 2023

Conversation

dgozman
Copy link
Contributor

@dgozman dgozman commented Sep 18, 2023

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.

@github-actions

This comment has been minimized.

@dgozman dgozman changed the title fix(tracing): support older traceV4 traces with consoleMessage.args fix(tracing): bump trace version to V5, migrate V4 traces to consoleMessage.args Sep 18, 2023
@dgozman dgozman force-pushed the trace-fix-console-new-version branch from 7755422 to ad8e6dc Compare September 18, 2023 22:49
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

packages/trace-viewer/src/traceModel.ts Outdated Show resolved Hide resolved
@dgozman dgozman force-pushed the trace-fix-console-new-version branch from e869cf3 to 815b18a Compare September 19, 2023 20:06
@github-actions

This comment has been minimized.

@dgozman dgozman force-pushed the trace-fix-console-new-version branch from 815b18a to 30b7181 Compare September 19, 2023 22:39
@github-actions
Copy link
Contributor

Test results for "tests 1"

8 flaky ⚠️ [chromium] › library/tracing.spec.ts:239:5 › should not include trace resources from the previous chunks
⚠️ [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
⚠️ [firefox] › page/page-goto.spec.ts:81:3 › should work with Cross-Origin-Opener-Policy
⚠️ [chromium] › library/tracing.spec.ts:239:5 › should not include trace resources from the previous chunks
⚠️ [webkit] › library/browsercontext-reuse.spec.ts:50:1 › should reset serviceworker
⚠️ [webkit] › library/inspector/cli-codegen-javascript.spec.ts:87:5 › should save the codegen output to a file if specified
⚠️ [webkit] › page/page-wait-for-navigation.spec.ts:85:3 › should work with clicking on links which do not commit navigation

25663 passed, 604 skipped
✔️✔️✔️

Merge workflow run.

@dgozman dgozman merged commit 2af7d67 into microsoft:main Sep 19, 2023
27 of 28 checks passed
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
…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]can not display trace
3 participants