Bug #15640
closed
[CWL] some tests failing with "jshint failed to run succesfully"
Added by Peter Amstutz over 5 years ago.
Updated about 5 years ago.
Estimated time:
(Total: 0.00 h)
Release relationship:
Auto
Related issues
1 (1 open — 0 closed)
- Subject changed from some CWL tests failing with "jshint failed to run succesfully" to [CWL] some tests failing with "jshint failed to run succesfully"
- Description updated (diff)
- Target version changed from 2019-09-25 Sprint to 2019-10-09 Sprint
- Assigned To set to Peter Amstutz
- Status changed from New to In Progress
Adjusted the memory assigned to the tests, they seem to be passing now.
A couple of takeaways
- It seems that jobs that use RunInSingleContainer need to have a minimum of ~128 MiB RAM assigned to ensure that cwltool and jshint can run, it might be a good idea to set a floor.
- The arvados-cwl-conformance-tests might be running tests from master instead of the provided githash, which would explain why my experiments didn't work, it wasn't running the modified test
15640-cwl-min-ram @ 861599984cc86e100bd1c6dc36500a6f2334052d
- RunInSingleContainer sets minimum RAM at 128 MiB
With less than 128 MiB, jshint (which is invoked by cwltool) crashes, so set a floor on the RAM request.
Any chance job_res_reqs won't have an entry for "ramMin"? If true, there should be a check that get doesn't return None.
Nevermind, I see that it gets added in get_overall_res_req via max_res_pars.
Other than that, this LGTM. Thanks!
- Related to Bug #15692: [CWL] test_with_arvbox integration tests use tests inside image added
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
Updated by 
Updated by Eric Biagiotti