@iloveeclipse @jjohnstn From 3 attempts I got 2 timeouts (and one unrelated intermittent failure).

Who decides about the timeout? It seems that the current limit of 40 min. is not realistic.

Who decides about the timeout? It seems that the current limit of 40 min. is not realistic.

See

Who decides about the timeout? It seems that the current limit of 40 min. is not realistic.

See

eclipse.jdt.ui/Jenkinsfile

Line 3 in 690340f

timeout(time: 40, unit: 'MINUTES')

Thanks, so the timeout has been at 40 since @ktatavarthi created that file 2 years ago (#1)

Asked differently: does everybody think this is the right threshold?

Looking at https://ci.eclipse.org/jdt/job/eclipse.jdt.ui-github/job/master/buildTimeTrend - normal build is usually around ~25 minutes. What we see is probably related to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4063#note_2472456 . Meanwhile it should be fine to bump it to e.g. 60 minutes (twice slower than average time) so people don't have to restart builds like that.

Looking at https://ci.eclipse.org/jdt/job/eclipse.jdt.ui-github/job/master/buildTimeTrend - normal build is usually around ~25 minutes. What we see is probably related to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4063#note_2472456 . Meanwhile it should be fine to bump it to e.g. 60 minutes (twice slower than average time) so people don't have to restart builds like that.

Thanks, will do if/when I run into this problem again in the near future :)