Kirk, most IntegrationTest jobs run in 25-30 minutes, but I did see one <https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/IntegrationTestOpenJDK11/builds/7202> that came in just under 45 minutes but did succeed. It would be nice to know what test is occasionally taking longer and why…
Here’s an example of a previous timeout increase (Note that both the job timeout and the callstack timeout should be increased by the same amount): https://github.com/apache/geode/pull/4231 > On Apr 16, 2020, at 10:47 AM, Kirk Lund <kl...@apache.org> wrote: > > Unfortunately, IntegrationTest exceeds timeout every time I trigger it. The > cause does not appear to be a specific test or hang. I > think IntegrationTest has already been running very close to the timeout > and is exceeding it fairly often even without my changes in #4963. > > Should we increase the timeout for IntegrationTest? (Anyone know how to > increase it?)
