Ok, let's just keep an eye on it for now. Thanks! On Thu, Jun 11, 2020 at 12:53 PM Owen Nichols <onich...@vmware.com> wrote:
> This timeout is separate from the test timeout. > > AcceptanceTest currently has a 90-minute timeout for running tests. > These tests usually take 60-65 minutes. > > The timeout you mentioned is just for uploading the report. It is > currently set at 1 hour, although normally only takes about 30 seconds. > Sometimes network connections just hang, but increasing timeout will not > help. If this happens a lot, a better approach might be a shorter timeout > and add a few retries for the report upload step. > > On 6/11/20, 11:29 AM, "Kirk Lund" <kl...@apache.org> wrote: > > I think we need to bump up the max time for AcceptanceTest jobs. > > Here's an example of an AcceptanceTest job hanging due to timeout in > archival (after the execution of tests already finished): > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-develop-main%2Fjobs%2FAcceptanceTestOpenJDK11%2Fbuilds%2F253%23A&data=02%7C01%7Conichols%40vmware.com%7C90e8ab7a6531401b29be08d80e356fcb%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637274969960758668&sdata=HXDYWMfcRGuOSdT%2FVjT%2FyZIGBoE3GzRijeUYs1ZATmU%3D&reserved=0 > >
