Closed Bug 1389049 Opened 7 years ago Closed 6 years ago

Reduce logging of Firefox components for geckodriver log

Categories

(Testing :: geckodriver, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1399441

People

(Reporter: whimboo, Unassigned)

Details

As formerly mentioned on bug 1384969 we have to reduce the logging given that it adds lots of irritation to people. Sadly turning of the pref "browser.dom.window.dump.enabled" was the wrong way doing it. So we have to figure out something else.

For example we could parse the stdout from Firefox and only let pass entries for Marionette. If doing so we should also have a flag for letting all pass through. Not sure if there is log level higher than trace.

On the other side there might still be a bug with logging in relation to Marionette. It doesn't seem to happen when using the client alone, but geckodriver. Maybe there is a pref we miss to set for the profile and first start of Firefox to prevent unnecessary logging.

Depending on how important this change is I could have a look into.
(In reply to Henrik Skupin (:whimboo) from comment #0)

> As formerly mentioned on bug 1384969 we have to reduce the logging
> given that it adds lots of irritation to people. Sadly turning of
> the pref "browser.dom.window.dump.enabled" was the wrong way doing
> it. So we have to figure out something else.

The intention of the patch that got backed out was to stop Browser
Console entries caused by web content errors from being printed to
stdout; not to stop stdout logging (using dump()) from Firefox in
general.
So this needs discussion. I will put it as an item for this weeks meeting on Wednesday.
Priority: -- → P3
I think we decided to resolve this by hiding the stdout/stderr from
Firefox by default.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.