-
Notifications
You must be signed in to change notification settings - Fork 16
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
Allow requesting RO-Crate provenance (next cwltool release) #166
Comments
Note that there isn't a easy workaround in Calrissian itself. Because of the way that |
Hi @davidjsherman, thanks for the heads-up. We've been following the cwltool issue and PR. Happy to merge when @mr-c releases cwltool and you're ready with the PR on calrissian |
Here's the new |
@fabricebrito would you prefer the Calrissian-specific unit test in a separate file, or folded into tests/test_job.py? |
@davidjsherman a separate file is perfect |
@davidjsherman is this issue still relevant? Linked to this issue, I've submitted a query here https://cwl.discourse.group/t/cwltool-provenance-worfklow-cwl-main-vs-workflow-cwl/948 |
@fabricebrito Yes, but making the PR has unfortunately been sitting in our backlog. I'll see whether I can nudge that along |
When we provide the results of Calrissian jobs as a deliverable, we include a RO-Crate that reports provenance of the results produced by the execution the CWL workflow. The provenance report is created by
cwltool
when the--provenance
folder
option is specified.Calrissian can pass through the option but this currently fails because Calrissian calls
cwltool.main
directly with preparsed arguments only and the current release ofcwltool
requires unparsed arguments as well when reporting provenance.The requirement for unparsed arguments has been removed by common-workflow-language/cwltool#1964, and the change should be in the next
cwltool
release.We could provide a PR with a unit test, as soon as the release is available.
The text was updated successfully, but these errors were encountered: