Since recently many build jobs for jdt.debug are being aborted at the timeout of 40 minutes, while previously a typical time to completion was below 30 minutes.
The list on https://ci.eclipse.org/jdt/job/eclipse.jdt.debug-github/job/master/ indicates that build times went up after #692 - already the PR build was aborted - but I have no idea if that change possibly brought such performance regression or whether all this is based only on "bad weather" on our build infra.
Anyone have a guess?
@SougandhS @subyssurendran666 @HannesWell @jarthana
Since recently many build jobs for jdt.debug are being aborted at the timeout of 40 minutes, while previously a typical time to completion was below 30 minutes.
The list on https://ci.eclipse.org/jdt/job/eclipse.jdt.debug-github/job/master/ indicates that build times went up after #692 - already the PR build was aborted - but I have no idea if that change possibly brought such performance regression or whether all this is based only on "bad weather" on our build infra.
Anyone have a guess?
@SougandhS @subyssurendran666 @HannesWell @jarthana