Ivan Mirić

I'm removing the `high prio` label from this since I'm not able to reproduce the original report from the forum, and a complaint of "not working" doesn't give sufficient information...

I haven't been able to reproduce it though :man_shrugging: I'm hoping that with the user's debug log we would be able to see more information, or you can pick this...

I tried it on `main` 24a8ffd (before #260 was merged) and wasn't able to reproduce it, but after trying your updated script it happened a couple of times now. So...

> Our script is not SPA (The one in #258: Flaky test script), and the problem still occurs. Again, we're not talking about the same issues. The one reported on...

A couple more observations: - It doesn't have anything to do with device emulation itself. You can comment that out and not pass any options to `browser.newContext()`, and it would...

This was fixed by #578! :tada: I can no longer reproduce it on `main` :)

Unlike browser downloads (#98), which happen entirely on the browser side AFAIU, this would return the PDF data to the JS script, right? From there the user could upload the...

I don't think this is an issue. I purposefully decided to not silence the error in cases when the browser process ends unexpectedly, since we do want to show an...

OK, I agree that it clutters the output in that case. I wasn't able to reproduce it with a single iteration, but it did happen when running with multiple iterations....

On second thought, I think this issue is a duplicate of #491. That `context deadline exceeded` is likely the same error as this timeout one, just before the logging improvements...