You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document how to use ./wpt run --verify locally #15013: when running ./wpt run --verify failed, there is no detailed output for stability results. Adding --log-mach - can fix it, so might consider changing the default value.
All the log-related options are passed to setup_logging function to set up the logger.
Meanwhile, the setup_logging removes all the log_* items from args after setting up the logger:
The args then is passed to wptserver. As a reults, in #15012: --log-*-level was not passed to wptserve module, as the wpt server has a log filter and it doesn't know anything of the log configuration from command line at the wpt server side:
There are needs to set default log configurations before passing them to
setup_logging
for./wpt run
. Here are some examples:--verbose
to be an alias of--log-mach-level debug
../wpt run --verify
locally #15013: when running./wpt run --verify
failed, there is no detailed output for stability results. Adding--log-mach -
can fix it, so might consider changing the default value.All the log-related options are passed to
setup_logging
function to set up the logger.Meanwhile, the
setup_logging
removes all thelog_*
items fromargs
after setting up the logger:wpt/tools/wptrunner/wptrunner/wptlogging.py
Lines 19 to 21 in 8ab29ab
The
args
then is passed towptserver
. As a reults, in #15012: --log-*-level was not passed to wptserve module, as the wpt server has a log filter and it doesn't know anything of the log configuration from command line at the wpt server side:wpt/tools/wptrunner/wptrunner/environment.py
Lines 149 to 165 in 8ab29ab
The text was updated successfully, but these errors were encountered: