common-workflow-language / common-workflow-language/cwltest
After N timeouts, abort tests
- Dominant language
- Python
- Stars
- 20
- Forks
- 19
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 3
Description
If we're running CWL conformance tests and there is a 15 minutes timeout per test. there are 133 tests so this ends up in a 33 hours total timeout when running against an unhealthy cluster.
Is there a way to parametrize "after N timeouts/fails, abort the tests and mark them as failed" ?
Thanks,
Nico
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CWL conformance test runner and how its 15-minute per-test timeout and failures are handled. Define where an N-timeout or failure threshold would be configured, then verify that reaching it stops the run and marks the remaining conformance tests as failed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100