-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout #4
Comments
Hi Aleksey, That looks strange as it seems to have timed out before the 70 seconds Venlig hilsen,
|
Hi, I got home from work and took another look at your problem. It seems your inner parallel flow, with a 20 second timeout is actually the one timing out. I could not reproduce this with such high timeouts, but by lowering the inner timeout to 5 seconds, I got the following: == Legend == Serial builds: [] Parallel builds: () Invoking (w/x,y/z): w=current invocation in current flow scope, x=max in scope, y=total number of invocations, z=total max invocations Elapsed time: 'after: x/y': x=time spent during current run of job, y=time elapsed since start of outermost flow Queuing jobs for serial run: [ Queuing job: ADMIN-flow-1 'ADMIN-flow-1' Status IDLE - latest build: ADMIN-flow-1 #3 Queuing jobs for parallel run: ( Queuing job: ADMIN-flow-2 'ADMIN-flow-2' Status IDLE - latest build: ADMIN-flow-2 #2 Queuing job: ADMIN-flow-3 'ADMIN-flow-3' Status IDLE - latest build: ADMIN-flow-3 #2 ) Queuing job: ADMIN-flow-1 'ADMIN-flow-1' Status IDLE - latest build: ADMIN-flow-1 #3 ] Invoking (1/1,1/1): ['ADMIN-flow-1', ('ADMIN-flow-2', 'ADMIN-flow-3'), 'ADMIN-flow-1'] Invoking (1/1,1/1): http://localhost:8080/job/ADMIN-flow-1 - /build 'ADMIN-flow-1' Status QUEUED - latest build: ADMIN-flow-1 #3 'ADMIN-flow-1' Status IDLE - latest build: ADMIN-flow-1 #4 SUCCESS: 'ADMIN-flow-1' - build: http://localhost:8080/job/ADMIN-flow-1/4/testReport/api/python/ after: 5.232s/5.232s Invoking (1/1,1/1): ('ADMIN-flow-2', 'ADMIN-flow-3') Invoking (1/1,1/1): http://localhost:8080/job/ADMIN-flow-2 - /build Invoking (1/1,1/1): http://localhost:8080/job/ADMIN-flow-3 - /build 'ADMIN-flow-2' Status QUEUED - latest build: ADMIN-flow-2 #2 'ADMIN-flow-2' Status QUEUED - latest build: ADMIN-flow-2 #2 Traceback (most recent call last): File "./aleksey.py", line 53, in main() File "./aleksey.py", line 51, in main ctrl1.invoke('flow-1') File "./../../jenkinsflow/jobcontrol.py", line 413, in __exit__ self.wait_for_jobs() File "./../../jenkinsflow/jobcontrol.py", line 383, in wait_for_jobs last_report_time = self._check(start_time, last_report_time) File "./../../jenkinsflow/jobcontrol.py", line 331, in _check last_report_time = job._check(start_time, last_report_time) File "./../../jenkinsflow/jobcontrol.py", line 263, in _check self._check_timeout(start_time) File "./../../jenkinsflow/jobcontrol.py", line 229, in _check_timeout raise FlowTimeoutException("Timeout after:" + self._time_msg(start_time) + unfinished_msg) jenkinsflow.jobcontrol.FlowTimeoutException: Timeout after:after: 5.383s/11.122sUnfinished jobs:('ADMIN-flow-2', 'ADMIN-flow-3') This is as expected, the inner flow timed out just after 5 seconds. I noticed in your example that flow-2 and three did not start in parallel. Have you got enough executors? It also seems that your jenkins is not performing well. My Jenkins finished the flow in 12 seconds. |
It may be a case of quite old Jenkins version that we're using here. I will try to run this on latest Jenkins. |
Hi!
In my Jenkins 1.484 I created 3 simple jobs: flow-1, flow-2 and flow-3. Each job does 'uname -a'.
I created simple flow:
And this happened:
Shall I increase timeout in this call?
Thanks!
The text was updated successfully, but these errors were encountered: