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: revert noWaitForFinish option, page.close does not wait for ro… #28658

Merged
merged 2 commits into from Dec 15, 2023

Conversation

yury-s
Copy link
Member

@yury-s yury-s commented Dec 14, 2023

…ute handlers

Reference #23781

packages/playwright-core/src/client/network.ts Outdated Show resolved Hide resolved
packages/playwright-core/src/client/page.ts Show resolved Hide resolved
@@ -703,7 +701,7 @@ export class RouteHandler {
// Note that context.route handler may be later invoked on a different page,
// so we only swallow errors for the current page's routes.
const handlerActivations = page ? this._activeInvocations.get(page) : [...this._activeInvocations.values()];
if (this.noWaitOnUnrouteOrClose || noWait) {
if (noWait) {
handlerActivations.forEach(h => h.ignoreException = true);
} else {
const promises = [];
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we still need the logic below about route._didThrow?

Copy link
Member Author

Choose a reason for hiding this comment

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

I believe we do as we should not be waiting for the handlers that threw an error already.

This comment has been minimized.

Copy link
Contributor

Test results for "tests 1"

2 flaky ⚠️ [chromium] › library/tracing.spec.ts:243:5 › should not include trace resources from the previous chunks
⚠️ [webkit] › library/tracing.spec.ts:243:5 › should not include trace resources from the previous chunks

21157 passed, 585 skipped
✔️✔️✔️

Merge workflow run.

@yury-s yury-s merged commit d89837c into microsoft:main Dec 15, 2023
30 checks passed
@yury-s yury-s deleted the revert-noWaitForActive branch December 15, 2023 17:00
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.

None yet

2 participants