rossoctl / rossoctl/workload-harness
--action-timeout not forwarded by deploy-and-evaluate.sh
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 5
- Forks
- 6
- Avg merge
- 11h 37m
- Merged PRs (30d)
- 1
Description
Summary
deploy-benchmark.sh accepts --action-timeout SECONDS but deploy-and-evaluate.sh (the wrapper) does not accept or forward the flag. Passing --action-timeout to the wrapper silently drops it.
Steps to reproduce
./deploy-and-evaluate.sh --action-timeout 120 ...
The flag is ignored; deploy-benchmark.sh runs with its default timeout.
Expected behaviour
deploy-and-evaluate.sh should accept --action-timeout and pass it through to deploy-benchmark.sh.
Found in
PR #33 review by @kellyaa.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with deploy-and-evaluate.sh and compare its argument handling with deploy-benchmark.sh, which already accepts --action-timeout SECONDS. Run ./deploy-and-evaluate.sh --action-timeout 120 ... and verify that deploy-benchmark.sh receives the flag and uses the requested timeout instead of its default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100