You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to set a job-level timeout for the entire job, not just per-step. This is vital for being able to use StepCI in a type of regular usage scheduled on a cron without having it "overlap" the next run.
What did you expect to happen?
If I could have a configuration such as...
version: "1.1"name: Sample Workflowtests:
example:
timeout: 20000# Max of 20 seconds for the entire jobsteps:
- name: Step 1 - Example Basic Auth with headers, and retrieshttp:
timeout: 10000retries: 1url: https://google.com/BasicAuthmethod: GETauth:
basic:
username: hellopassword: worldcheck:
status: "/^20/"
- name: Step 2 - Example with paramshttp:
timeout: 10000url: https://google.com/QueryParamsmethod: GETparams:
hello: worldworld: hellocheck:
status: "/^20/"
- name: Step 3 - CSS Selectorhttp:
timeout: 10000url: https://google.com/QueryParamsmethod: GETcheck:
selectors:
title: Google
With this above configuration, your run would never take longer than 20 seconds, even though you have enough timeouts in the 3 steps present which COULD take it to 30 seconds. But because of the global timeout, if all the different steps timeout and take their max time, by the end of the second one the job will exit out (having had 20 seconds go by) and it would never execute the third one.
Version
HEAD/Latest as of Jan 15, 2023
Environment
node: ~18.x
How can we reproduce this bug?
No response
Relevant log output
No response
Would you be interested in working on a bugfix for this issue?
Yes! Assign me
The text was updated successfully, but these errors were encountered:
@mishushakov Timing it out elsewhere isn't handling it gracefully with a proper resultset map about the failure and what occurred and at what step it failed/stalled at. That doesn't really solve the underlying issue.
Note: I'd be happy to sponsor someone to add this feature if anyone's down
What happened?
I'd like to be able to set a job-level timeout for the entire job, not just per-step. This is vital for being able to use StepCI in a type of regular usage scheduled on a cron without having it "overlap" the next run.
What did you expect to happen?
If I could have a configuration such as...
With this above configuration, your run would never take longer than 20 seconds, even though you have enough timeouts in the 3 steps present which COULD take it to 30 seconds. But because of the global timeout, if all the different steps timeout and take their max time, by the end of the second one the job will exit out (having had 20 seconds go by) and it would never execute the third one.
Version
HEAD/Latest as of Jan 15, 2023
Environment
node: ~18.x
How can we reproduce this bug?
No response
Relevant log output
No response
Would you be interested in working on a bugfix for this issue?
The text was updated successfully, but these errors were encountered: