[
https://issues.apache.org/jira/browse/GEODE-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-8740:
--------------------------------
Description:
Recently UpgradeTestOpenJDK8 has been taking ~59 minutes and its job timeout is
1h. After adding 1.13.1 as old version, it tipped to taking slightly over an
hour on JDK8 (which is why it wasn't caught in PR, which only checks JDK11).
Timeout for this job should be increased to 1h30m as there's no need to cut it
so close.
Recent changes to Benchmarks have also caused longer runs (from 4h -> 7h in the
best case, and much much longer in the worst case). The current job timeout of
8h is being hit frequently, and after trying a temporary increase to 16h, we
still saw successful runs taking 15h, and still some timing out...
was:
Recently UpgradeTestOpenJDK8 has been taking ~59 minutes and its job timeout is
1h. After adding 1.13.1 as old version, it tipped to taking slightly over an
hour. Timeout for this job should be increased to 1h30m as there's no need to
cut it so close.
Recent changes to Benchmarks have also caused longer runs (from 4h -> 7h in the
best case, and much much longer in the worst case). The current job timeout of
8h is being hit frequently, and after trying a temporary increase to 16h, we
still saw successful runs taking 15h, and still some timing out...
> increase test job timeouts
> --------------------------
>
> Key: GEODE-8740
> URL: https://issues.apache.org/jira/browse/GEODE-8740
> Project: Geode
> Issue Type: Improvement
> Components: ci
> Reporter: Owen Nichols
> Priority: Major
> Labels: pull-request-available
>
> Recently UpgradeTestOpenJDK8 has been taking ~59 minutes and its job timeout
> is 1h. After adding 1.13.1 as old version, it tipped to taking slightly over
> an hour on JDK8 (which is why it wasn't caught in PR, which only checks
> JDK11). Timeout for this job should be increased to 1h30m as there's no need
> to cut it so close.
> Recent changes to Benchmarks have also caused longer runs (from 4h -> 7h in
> the best case, and much much longer in the worst case). The current job
> timeout of 8h is being hit frequently, and after trying a temporary increase
> to 16h, we still saw successful runs taking 15h, and still some timing out...
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
