-
-
Notifications
You must be signed in to change notification settings - Fork 311
web-test-runner: DynamicTerminal can swallow errors #2927
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
Comments
I didn't encounter such issues myself. Can you make some screenshots showing what you expected to see in the console and what was missing? A link to a repository with this particular test setup can also help a lot. |
It's a little difficult to reproduce, unless you build our whole repository with Bazel involved 😄 — I could potentially try to work on a simpler reproduction. The error I've fixed with #2928, was basically swallowed because it was an uncaught error due to the incorrect I've then enabled Puppeteer debug logging and traced back that
Based on this experience, I feel like the DynamicTerminal is great for TTY's but there should be a whole new implementation for static logging that never involves clearing, patching of |
I'm afraid I don't know the context well enough to imagine this behavior based on provided description. |
I've been trying to use Web Test Runner with our Bazel build system. This means Web Test Runner may be invoked multiple times, executing multiple tests concurrently, with isolated instances of WTR.
This worked great overall, but we've noticed some instability/flakiness with the Puppeteer/
web/test-runner-chome
launcher and it was extremely hard to debug and required lots of patching of@web/test-runner-core
to actually see what is going on. The problem is that, even in non TTY mode, with static logging option enabled, the dynamic terminal logic was swallowing the errors— likely due to the regular clears() or dynamic logging that is still happening even withstaticLogging: true
.It would be great to improve the logic around logging here, to make it more CI/non TTY friendly.
The text was updated successfully, but these errors were encountered: