-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cromwell API tests to dos #33
Comments
@seankross in above item starting with
I'm embarrassed to admit I don't remember what this was about. Do you? In the tests that run cromwell via java that you and taylor started we are using the options.json files if it exists that have caching config in them. We're not currently using those if they exist in these api tests yet, but can do. |
I do want to use the options.json files in the api tests if they exist. Does that answer your question? |
I think that was it - to use any caching options in an input file. I'll add this functionality to the code |
…n files when submitting cromwell jobs; tweak helper funs
submit_wdls
fixture inconftest.py
: speed up submission if possible. Tryasyncio
andhttpx.AsyncClient
#35/api/womtool/{version}/describe
/api/workflows/{version}/{id}/abort
cromwell_glob
is used in the app - this function (and many others inrcromwell
) all use the/api/workflows/{version}/{id}/metadata
route - see those variousrcromwell
fxns for use cases to cover/api/workflows/{version}/query
/api/workflows/{version}/{id}/outputs
cromwell_failures
- uses /metadata w/ query params?includeKey=failures&includeKey=jobId
cromwell_call
- uses /metadata w/ query params?expandSubWorkflows=true
cromwell_labels
/api/workflows/{version}/{id}/labels
The text was updated successfully, but these errors were encountered: