Closed ruchim closed 1 year ago
@bshifaw not sure if #259 fixes this
Hi @ruchim,
I see you are running cromshell-alpha
, could you try installing the latest version of cromshell on RW. One way to do this is through 'pip install git+https://github.com/broadinstitute/cromshell.gitand try logs again. (the recent release is called via
cromshellas opposed to
cromshell-alpha`)
Tried an update (i can confirm i'm using cromshell 2.0.0)! The logging level is so much nicer (yay!) Still same issue with using the logs
command tho
jupyter@c1b74825647d:~$ cromshell status test-1
__
.,-;-;-,. /'_\
_/_/_/_|_\_\) /
'-<_><_><_><_>=/\
`/_/====/_/-'\_\
"" "" ""
{"status":"Succeeded",
"id":"3f1287e8-6442-43e5-b8b9-a81daf4a1a33"}
jupyter@c1b74825647d:~$ cromshell logs test-1
No logs with status ['Failed'] found for workflow, try adding the argument '-s ALL' to list logs with any status
jupyter@c1b74825647d:~$ cromshell version
cromshell 2.0.0
This looks good.
By default, the logs
command will retrieve the logs of tasks with the "Failed " status. Since the workflow being checked here completed with the status of "Succeeded", the logs command wont find any failed tasks and will exit with
No logs with status ['Failed'] found for workflow, try adding the argument '-s ALL' to list logs with any status
This default was set because we assume users are mainly looking at the logs of a workflow because they want to investigate a failure.
I'm trying to use Cromshell from the AoU RWB
I ran a workflow and status succeeded (bold)
Then, when I go to get logs, it fails and the stacktrace (see below) isn't very clear to me. Trying to debug how to fix the logs functionality
> jupyter@5cbce7741997:~$ cromshell-alpha status c47be75c-ba47-4b9e-99a8-8e5cf5d70bc4 2023-05-12 16:23:52,910 cromshell.main INFO Invoked by: /opt/conda/bin/cromshell-alpha status c47be75c-ba47-4b9e-99a8-8e5cf5d70bc4