Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable status to work on multiple directories or wildcards #257

Closed
crkrenn opened this issue Apr 30, 2020 · 0 comments · Fixed by #301
Closed

enable status to work on multiple directories or wildcards #257

crkrenn opened this issue Apr 30, 2020 · 0 comments · Fixed by #301
Labels
enhancement Good First Issue If you're looking to get involved, these are good places to start!

Comments

@crkrenn
Copy link
Contributor

crkrenn commented Apr 30, 2020

A very common use case for our work is to check on multiple simulations or sets of simulations.

But maestro status only takes a single directory as an argument.

Can this be changed so that it can take one or more directories as arguments.

This works:

[crkrenn@rztopaz188 studies]$ maestro status ares-template_20200429-1*8
Step Name    Workspace    State    Run Time    Elapsed Time    Start Time    Submit Time                 End Time                      Number Restarts
-----------  -----------  -------  ----------  --------------  ------------  --------------------------  --------------------------  -----------------
run-model    run-model    FAILED   --:--:--    0d:00h:01m:00s  --            2020-04-29 17:08:35.169251  2020-04-29 17:09:35.294178                  0

But this does not:

[crkrenn@rztopaz188 studies]$ maestro status ares-template_20200429-1*8 ares-template_20200429-1*0
usage: maestro [-h] [-l LOGPATH] [-d DEBUG_LVL] [-c] [-v]
               {cancel,run,status} ...
maestro: error: unrecognized arguments: ares-template_20200429-165920
@FrankD412 FrankD412 added enhancement Good First Issue If you're looking to get involved, these are good places to start! labels May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Good First Issue If you're looking to get involved, these are good places to start!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants