diff options
author | dpranke@google.com <dpranke@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-11 00:17:41 +0000 |
---|---|---|
committer | dpranke@google.com <dpranke@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-11 00:17:41 +0000 |
commit | 58b8903b7e8382824cfdb986a4ce5aad6f40c221 (patch) | |
tree | 6529cf16208bdb82cb06959a8daa15c87bce4dfd /base/base_paths_win.cc | |
parent | c488a549682af9b388542bda791f92e53dc01c9d (diff) | |
download | chromium_src-58b8903b7e8382824cfdb986a4ce5aad6f40c221.zip chromium_src-58b8903b7e8382824cfdb986a4ce5aad6f40c221.tar.gz chromium_src-58b8903b7e8382824cfdb986a4ce5aad6f40c221.tar.bz2 |
Logging cleanup for run_webkit_tests. This significantly revises the output
to run_webkit_tests.
First, a number of log messages have had their levels changed (mostly to
make them quieter).
Second, the script outputs a "meter" that shows progress through the
test run, which is a one line summary of where it's at current
(e.g. "parsing expectations", "gathering files". During the actual test
execution, the meter displays "%d tests completed as expected, %d didn't,
%d remain". The meter uses carriage returns but no linefeeds, so the output
is overwritten as it progresses. The meter is disabled if --verbose is
specified, to avoid unnecessary confusion.
Third, I removed the --find-baselines option. I think I was the only one
using it, and --sources is good enough (but added the baseline for
the checksum as well as the .png when using --sources).
Fourth, there is a new "--log" option that can be used to provide finer
granularity of logging. It accepts a comma-separated list of options, like:
--log 'actual,expected,timing':
"actual": the actual test results (# of failures by type and timeline)
"config": the test settings (results dir, platform, etc.)
"expected": the results we expected by type and timeline
"timing": test timing results (slow files, total execution, etc.)
All of this information is logged at the logging.info level (if the appropriate option is enabled).
Using the --verbose switch will cause all of options to be logged, as well
as the normal verbose output. In addition, the verbose output will disable
the meter (as mentioned above). Note that the "actual" results will be logged
to stdout, not stderr, for compatibility with the buildbot log parser.
Finally, the list of unexpected results (if any) will be logged to stdout,
along with a one-line summary of the test run.
The net result is that when run with no command line options (and when no
tests fail), only one line of output will be produced.
R=ojan@chromium.org,pam@chromium.org
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/465089
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34310 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/base_paths_win.cc')
0 files changed, 0 insertions, 0 deletions