-
Notifications
You must be signed in to change notification settings - Fork 57
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
Avoid stderr pollution from chrome/electron logging #132
Comments
This can be done by consumers fairly easily be appending |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At this moment, while running tests, almost on any platforms, there are a series of notifications or warnings coming from chrome that cannot be addressed. These cannot really be addressed and they make reading the console considerably harder, especially as they are generated by a different process and they appear at random locations in output.
I investigated a redirection of stderr and it seems to be considerably improve the experience. Example of thing that no longer populated the console:
I am not saying that we should sent this to
/dev/null
, just that we should dump it to anstderr.log
instead, so it can be analyzed if really needed.The text was updated successfully, but these errors were encountered: