Bug 2047607 - fix: allow to set remote.log.level from --pref#101
Merged
Conversation
Collaborator
Author
|
Alternatively we could also introduce a dedicated command line argument (eg That being said, it implies users have to know about |
Collaborator
Author
|
Tagging @padenot for review, since this is about getting better logs :) |
padenot
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a known limitation from geckodriver, which has to be able to drive the log level independently and does that by setting the preference
remote.log.level.The patch checks if
remote.log.levelis present in the user-provided preferences, and if so, translates the value to a geckodriver log level.