Resource allocation (CPU/memory/ retries/time)

[sitapriyamoorthi]

If CPU,retries, time and memory allocations are correctly handled

[tefirman]

@sitapriyamoorthi -- I believe this functionality is demonstrated in "helloDockerHostname.wdl", do you agree?

[sitapriyamoorthi]

@tefirman yes i think the "helloDockerHostname.wdl" does test the ability to spin up a docker and use of the specified memory allocations.

I guess what is missing in this test (or could be added into the WDL) would be testing these use cases:

1. Testing dynamic run time variables ( a user provides dynamic values as inputs) and making sure that these are actually allocated?

2. Checking if custom runtime variables are actually used ?

3. Invalid runtime variables returning a valid meaningful error (but a successful WDL run)

4. Also probably need to test and validate successful docker pull from different sources?

• Testing different versions (latest versus x.x.x)
• Testing fall back mechanism if primary docker source fails?
• Testing public versus private resources

5. Also would think about testing JSON files providing custom variables and making sure those are getting utilized as well?

Totally might be an overkill but would be a potentially good way to monitor resource allocations are appropriately being given on the cluster.

I know we also need to test the GPU allocations but I know that there is an issue with testing those with GitHub actions and we potentially needs to create a test and independently check this?

I am going to rename this issue to test in-line (inside the WDL) testing and convert the otherone to test from JSON files that way we have two independent lines of testing. Let me know if that makes sense?