Skip to content

Commit 9f4da5c

Browse files
committed
Update readme for result failures tool.
Updating the readme to better give a quick overview of how to use the results failures tool. Bug: Change-Id: Id6d4492e6a55e651886e9ccbbc88965248e1ac88 Reviewed-on: https://dart-review.googlesource.com/16740 Reviewed-by: William Hesse <[email protected]>
1 parent 6a0ef10 commit 9f4da5c

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

tools/gardening/README.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,17 @@ each test against the status files in your repository. Use it by calling:
2525

2626
`dart results.dart get failures <argument>`
2727

28-
The argument can be a builder-group, a specific builder, a builder and a
29-
build-number, a CL number and patchset, or an uri to a result.log file.
28+
The arguments can be one of the following:
29+
30+
```console
31+
get failures <result.log> : for a local result.log file.
32+
get failures <uri_to_result_log> : for direct links to result.logs.
33+
get failures <uri_try_bot> : for links to try bot builders.
34+
get failures <commit_number> <patchset> : for links to try bot builders (see example below).
35+
get failures <builder> : for a builder name.
36+
get failures <builder> <build_number> : for a builder and build number.
37+
get failures <builder_group> : for a builder group.
38+
```
3039

3140
Some common workflows are listed below.
3241

0 commit comments

Comments
 (0)