squakez commented on PR #6881: URL: https://github.com/apache/camel-k/pull/6881#issuecomment-6162531865
> Good point @squakez I took another look at the difference between the runs. > > It turns out `nightly-multi.yml` doesn't set `CAMEL_K_TEST_TIMEOUT_SHORT`, so it runs with the default 1-minute timeout (`TestTimeoutShort = 1m`). In other workflows like `common.yml` and `nightly-release.yml`, that timeout is set to 2 minutes, which is why they don't hit the 60-second limit. > > On the ARM / JDK 21 runner, the pod log scraping took just over a minute, hitting that 60s cap. Would you prefer aligning the timeouts in `nightly-multi.yml` with the other workflows, or should we adjust the test timeout directly in `log_test.go`? Nice catch. I think we need to do both. Aligning the timeout as in other workflows, but also have a wider timeout (medium) in the affected log test. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
