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

Failures doesn't appear to work anymore #35

Closed
sckott opened this issue Mar 18, 2024 · 4 comments
Closed

Failures doesn't appear to work anymore #35

sckott opened this issue Mar 18, 2024 · 4 comments
Labels
investigating Still assessing priority, ignore for now v1.1 Should be implemented in PROOF v1.1

Comments

@sckott
Copy link
Member

sckott commented Mar 18, 2024

@vortexing Perhaps at one time failures worked but the function doesn't return anything anymore.

Even using the old version of the function before I arrived doesn't change anything.

The function pulls out calls https://github.com/getwilds/rcromwell/blob/main/R/cromwellFailures.R#L37 - but the data on failures appears to be in the slot failures instead.

But because I still don't have a good array of examples it's possible I'm missing cases where failures are returned in the calls slot?

Possibly this change from the changelog ? https://github.com/broadinstitute/cromwell/blob/develop/CHANGELOG.md#call-caching-failure-messages-5095

If you look at the swagger docs for a running cromwell server there is a route api/workflows/v1/{workflow_id}/metadata/failed-jobs, but it's not in the Cromwell docs https://cromwell.readthedocs.io/en/stable/api/RESTAPI/ - and that route returns data in the swagger docs interactive thing, BUT NOT when you do the same http request ANYWHERE else. Super not frustrating :flip-table:

@sckott sckott added the bug Something isn't working label Mar 18, 2024
@vortexing
Copy link
Member

Yes, it's entirely possible that cromwellFailures was developed before V45 Cromwell. However, I am 95% sure that the shiny app populates failed jobs. ok I just tested it in the shiny app and it does return results!! You should fail more. @sitapriyamoorthi and I have lots of failures to give you.

@sckott
Copy link
Member Author

sckott commented Mar 18, 2024

@sitapriyamoorthi can you provide some files that will fail that DO give you failure data in the shiny app?

@tefirman
Copy link
Member

tefirman commented Jul 30, 2024

@sckott -- The failures metadata seems to come through fine for me in both the "Job Failures" table in the Shiny app and via cromwell_failures in rcromwell (see screenshots below). As an example, try submitting this modified version of the HelloDocker WDL: helloDockerHostname.txt

It just tries to remove a nonexistent file within its main task which will cause it to error out and fail. Can you try this again?

image
image

@tefirman tefirman added the investigating Still assessing priority, ignore for now label Jul 30, 2024
@sckott
Copy link
Member Author

sckott commented Aug 7, 2024

Thanks @tefirman

That example works for me just as you laid out. nice.

Okay, not sure what happened, but seems to be working, so i'll close this after removing some comments in the code as reminder about this

@sckott sckott removed the bug Something isn't working label Aug 7, 2024
@sckott sckott added this to the rcromwell v3.2.4 milestone Aug 8, 2024
@sckott sckott added the v1.1 Should be implemented in PROOF v1.1 label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating Still assessing priority, ignore for now v1.1 Should be implemented in PROOF v1.1
Projects
No open projects
Status: Todo
Development

No branches or pull requests

3 participants