|
|
Chromium Code Reviews
Description[Findit] Adding script for custom try job queries
BUG=619637
Usage:
python try_job_data_metrics.py [args] where args can be:
-t: Separates try job by type (compile, test).
-m: Aggregates data by each master (chromium.chrome, chromium.linux, etc)
-b: Aggregates data by master and builder. Note passing this argument has the effect of breaking down by master first, then by builder.
-r: Whether or not heuristic results were used to guide the try job
-c: Whether or not compile targets were identified to speed up compile
For example:
python try_job_data_metrics.py
try_jobs_per_day: ...
average_regression_range_size: ...
average_execution_time: ...
average_commits_analyzed: ...
longest_execution_time: ...
shortest_execution_time: ...
number_of_try_jobs: ...
detection_rate: ...
error_rate: ...
time_per_revision: ...
under_five_minutes_rate: ...
under_fifteen_minutes_rate: ...
under_thirty_minutes_rate: ...
over_thirty_minutes_rate: ...
python try_job_metrics.py -t
Compile:
<stats ...>
Test:
<stats ...>
python try_job_metrics.py -t -m
Compile:
chromium.chrome:
<stats ...>
chromium.linux:
<stats ...>
...
Test:
chromium.chrome:
<stats ...>
...
Committed: https://chromium.googlesource.com/infra/infra/+/0539a5da9122baf2b74dd6ea7684d9121e3f8b2b
Patch Set 1 #
Total comments: 2
Patch Set 2 : Addressing comments #Patch Set 3 : Fixing gpylint issues #Messages
Total messages: 19 (10 generated)
Description was changed from ========== [Findit] Adding script to query try job data in detail [Findit] Adding script for custom try job queries BUG= ========== to ========== [Findit] Adding script for custom try job queries BUG= ==========
lijeffrey@chromium.org changed reviewers: + chanli@chromium.org, stgao@chromium.org
ptal
Description was changed from
==========
[Findit] Adding script for custom try job queries
BUG=
==========
to
==========
[Findit] Adding script for custom try job queries
BUG=619637
Usage:
python try_job_data_metrics.py [args] where args can be:
--type: Separates try job by type (compile, test).
--per-master: Aggregates data by each master (chromium.chrome, chromium.linux,
etc)
--per-builder: Aggregates data by master and builer. Note passing this argument
has the effect of breaking down by master first, then by builder.
--has-heuristic-results: Whether or not heuristic results were used to guide the
try job
--has-compile-targets: Whether or not compile targets were identified to speed
up compile
For example:
python try_job_data_metrics.py
try_jobs_per_day: ...
average_regression_range_size: ...
average_execution_time: ...
average_commits_analyzed: ...
longest_execution_time: ...
shortest_execution_time: ...
number_of_try_jobs: ...
detection_rate: ...
error_rate: ...
time_per_revision: ...
under_five_minutes_rate: ...
under_fifteen_minutes_rate: ...
under_thirty_minutes_rate: ...
over_thirty_minutes_rate: ...
python try_job_metrics.py --type
Compile:
<stats ...>
Test:
<stats ...>
python try_job_metrics.py --type --per-master
Compile:
chromium.chrome:
<stats ...>
chromium.linux:
<stats ...>
...
Test:
chromium.chrome:
<stats ...>
...
==========
On 2016/06/09 04:37:47, lijeffrey wrote: > ptal lgtm
lgtm with a comment https://codereview.chromium.org/2056623002/diff/1/appengine/findit/util_scrip... File appengine/findit/util_scripts/remote_queries/try_job_data_metrics.py (right): https://codereview.chromium.org/2056623002/diff/1/appengine/findit/util_scrip... appengine/findit/util_scripts/remote_queries/try_job_data_metrics.py:367: args = sys.argv[1:] If we can't use https://docs.python.org/2/howto/argparse.html for the order of switches, we'd better add a switch --help to print out all available options with usage explanation.
Description was changed from
==========
[Findit] Adding script for custom try job queries
BUG=619637
Usage:
python try_job_data_metrics.py [args] where args can be:
--type: Separates try job by type (compile, test).
--per-master: Aggregates data by each master (chromium.chrome, chromium.linux,
etc)
--per-builder: Aggregates data by master and builer. Note passing this argument
has the effect of breaking down by master first, then by builder.
--has-heuristic-results: Whether or not heuristic results were used to guide the
try job
--has-compile-targets: Whether or not compile targets were identified to speed
up compile
For example:
python try_job_data_metrics.py
try_jobs_per_day: ...
average_regression_range_size: ...
average_execution_time: ...
average_commits_analyzed: ...
longest_execution_time: ...
shortest_execution_time: ...
number_of_try_jobs: ...
detection_rate: ...
error_rate: ...
time_per_revision: ...
under_five_minutes_rate: ...
under_fifteen_minutes_rate: ...
under_thirty_minutes_rate: ...
over_thirty_minutes_rate: ...
python try_job_metrics.py --type
Compile:
<stats ...>
Test:
<stats ...>
python try_job_metrics.py --type --per-master
Compile:
chromium.chrome:
<stats ...>
chromium.linux:
<stats ...>
...
Test:
chromium.chrome:
<stats ...>
...
==========
to
==========
[Findit] Adding script for custom try job queries
BUG=619637
Usage:
python try_job_data_metrics.py [args] where args can be:
-t: Separates try job by type (compile, test).
-m: Aggregates data by each master (chromium.chrome, chromium.linux, etc)
-b: Aggregates data by master and builder. Note passing this argument has the
effect of breaking down by master first, then by builder.
-r: Whether or not heuristic results were used to guide the try job
-c: Whether or not compile targets were identified to speed up compile
For example:
python try_job_data_metrics.py
try_jobs_per_day: ...
average_regression_range_size: ...
average_execution_time: ...
average_commits_analyzed: ...
longest_execution_time: ...
shortest_execution_time: ...
number_of_try_jobs: ...
detection_rate: ...
error_rate: ...
time_per_revision: ...
under_five_minutes_rate: ...
under_fifteen_minutes_rate: ...
under_thirty_minutes_rate: ...
over_thirty_minutes_rate: ...
python try_job_metrics.py -t
Compile:
<stats ...>
Test:
<stats ...>
python try_job_metrics.py -t -m
Compile:
chromium.chrome:
<stats ...>
chromium.linux:
<stats ...>
...
Test:
chromium.chrome:
<stats ...>
...
==========
https://codereview.chromium.org/2056623002/diff/1/appengine/findit/util_scrip... File appengine/findit/util_scripts/remote_queries/try_job_data_metrics.py (right): https://codereview.chromium.org/2056623002/diff/1/appengine/findit/util_scrip... appengine/findit/util_scripts/remote_queries/try_job_data_metrics.py:367: args = sys.argv[1:] On 2016/06/13 23:48:21, stgao wrote: > If we can't use https://docs.python.org/2/howto/argparse.html for the order of > switches, we'd better add a switch --help to print out all available options > with usage explanation. Done.
comments addressed, ptal
The CQ bit was checked by lijeffrey@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from chanli@chromium.org, stgao@chromium.org Link to the patchset: https://codereview.chromium.org/2056623002/#ps20001 (title: "Addressing comments")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2056623002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: Infra Presubmit on tryserver.infra (JOB_FAILED, https://build.chromium.org/p/tryserver.infra/builders/Infra%20Presubmit/build...)
The CQ bit was checked by lijeffrey@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from chanli@chromium.org, stgao@chromium.org Link to the patchset: https://codereview.chromium.org/2056623002/#ps40001 (title: "Fixing gpylint issues")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2056623002/40001
Message was sent while issue was closed.
Description was changed from
==========
[Findit] Adding script for custom try job queries
BUG=619637
Usage:
python try_job_data_metrics.py [args] where args can be:
-t: Separates try job by type (compile, test).
-m: Aggregates data by each master (chromium.chrome, chromium.linux, etc)
-b: Aggregates data by master and builder. Note passing this argument has the
effect of breaking down by master first, then by builder.
-r: Whether or not heuristic results were used to guide the try job
-c: Whether or not compile targets were identified to speed up compile
For example:
python try_job_data_metrics.py
try_jobs_per_day: ...
average_regression_range_size: ...
average_execution_time: ...
average_commits_analyzed: ...
longest_execution_time: ...
shortest_execution_time: ...
number_of_try_jobs: ...
detection_rate: ...
error_rate: ...
time_per_revision: ...
under_five_minutes_rate: ...
under_fifteen_minutes_rate: ...
under_thirty_minutes_rate: ...
over_thirty_minutes_rate: ...
python try_job_metrics.py -t
Compile:
<stats ...>
Test:
<stats ...>
python try_job_metrics.py -t -m
Compile:
chromium.chrome:
<stats ...>
chromium.linux:
<stats ...>
...
Test:
chromium.chrome:
<stats ...>
...
==========
to
==========
[Findit] Adding script for custom try job queries
BUG=619637
Usage:
python try_job_data_metrics.py [args] where args can be:
-t: Separates try job by type (compile, test).
-m: Aggregates data by each master (chromium.chrome, chromium.linux, etc)
-b: Aggregates data by master and builder. Note passing this argument has the
effect of breaking down by master first, then by builder.
-r: Whether or not heuristic results were used to guide the try job
-c: Whether or not compile targets were identified to speed up compile
For example:
python try_job_data_metrics.py
try_jobs_per_day: ...
average_regression_range_size: ...
average_execution_time: ...
average_commits_analyzed: ...
longest_execution_time: ...
shortest_execution_time: ...
number_of_try_jobs: ...
detection_rate: ...
error_rate: ...
time_per_revision: ...
under_five_minutes_rate: ...
under_fifteen_minutes_rate: ...
under_thirty_minutes_rate: ...
over_thirty_minutes_rate: ...
python try_job_metrics.py -t
Compile:
<stats ...>
Test:
<stats ...>
python try_job_metrics.py -t -m
Compile:
chromium.chrome:
<stats ...>
chromium.linux:
<stats ...>
...
Test:
chromium.chrome:
<stats ...>
...
Committed:
https://chromium.googlesource.com/infra/infra/+/0539a5da9122baf2b74dd6ea7684d...
==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001) as https://chromium.googlesource.com/infra/infra/+/0539a5da9122baf2b74dd6ea7684d... |
