guild runs list [OPTIONS]
Run lists may be filtered using a variety of options. See below for details.
By default, the last 20 runs are shown. Use
-a, --all to show all runs, or
-m to show more 20 more runs. You may use
-m multiple times.
Run indexes are included in list output for a specific listing, which is based on the available runs, their states, and the specified filters. You may use the indexes in run selection commands (e.g.
compare, etc.) but note that these indexes will change as runs are started, deleted, or run status changes.
To show run detail, use
Filter by Operation or Label
Runs may be filtered by operation using
--operation. A run is only included if any part of its full operation name, including the package and model name, matches the value.
--label to only include runs with labels matching a specified value.
--label may be used multiple times to expand the runs that are included.
--unlabeled to only include runs without labels. This option may not be used with
--marked to only include marked runs.
Filter by Run Status
Runs may also be filtered by specifying one or more status filters:
--terminated. These may be used together to include runs that match any of the filters. For example to only include runs that were either terminated or exited with an error, use
--terminated --error, or the short form
Status filters are applied before
RUN indexes are resolved. For example, a run index of
1 is the latest run that matches the status filters.
Filter by Run Start Time
--started to limit runs to those that have started within a specified time range.
IMPORTANT: You must quote RANGE values that contain spaces. For example, to filter runs started within the last hour, use the option:
--selected 'last hour'
You can specify a time range using several different forms:
between DATETIME and DATETIME
last N minutes|hours|days
N days|weeks|months|years ago
DATETIME may be specified as a date in the format
YY-MM-DD (the leading
YY- may be omitted) or as a time in the format
HH:MM (24 hour clock). A date and time may be specified together as
between DATETIME and DATETIME, values for
DATETIME may be specified in either order.
When specifying values like
hours the training
s may be omitted to improve readability. You may also use
min instead of
hr instead of
between 1-1 and 4-30
between 10:00 and 15:00
last 30 min
last 6 hours
3 weeks ago
Filter by Source Code Digest
To show runs for a specific source code digest, use
--digest with a complete or partial digest value.
Show Deleted Runs
--deleted to show deleted runs. You can use the listing for run IDs and indexes to use in
runs restore (restore runs) and
runs purge (permanently delete runs).
Show Archived Runs
--archive to show runs in an archive directory. This option may not be used with
Show Remote Runs
To list runs on a remote, specify
--remote REMOTE. Use
guild remotes to list available remotes.
For information on configuring remotes, see
||Show all runs (by default only the last 20 runs are shown).|
||Show 20 more runs. Maybe used multiple times.|
||Limit number of runs shown.|
||Show deleted runs.|
||Show archived runs in DIR.|
||Filter runs with operations matching
||Filter runs with labels matching
||Filter only runs without labels.|
||Filter only marked runs.|
||Filter only unmarked runs.|
||Filter only runs that are still running.|
||Filter only completed runs.|
||Filter only runs that exited with an error.|
||Filter only runs terminated by the user.|
||Filter only pending runs.|
||Filter only staged runs.|
||Filter only runs started within RANGE. See above for valid time ranges.|
||Filter only runs with a matching source code digest.|
||Format runs as JSON.|
||Show run details.|
||List runs on REMOTE rather than local runs.|
||Show this message and exit.|
Guild AI version 0.7.0.post1