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
Flaky test: request proxy should proxy requests when configured #8644
Labels
Comments
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
OrKoN
added a commit
that referenced
this issue
Aug 10, 2022
Two main sources of flakiness addressed: 1) we should dispose the lifecycle watcher after we waited for the navigation response (bad API? we need to refactor but I think it'd be valuable to stabilize tests first without too many changes). 2) we should wait for the navigation request's response if there is a navigation request in the watcher. Closes #8644
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Also, the test
request proxy should respect proxy bypass list
:The latest occurence is in
npm run test:chrome:headless
on Linux, Node 18: https://github.com/puppeteer/puppeteer/runs/7232316868?check_suite_focus=trueThe text was updated successfully, but these errors were encountered: