tadayosi opened a new issue, #3777: URL: https://github.com/apache/camel-k/issues/3777
https://github.com/apache/camel-k/issues/3774#issuecomment-1291483813_ > I think that kind of timeout starts becoming a problem. 2 hours seems to be too long. At least we should try to have the native tests starting before everything else, so, the rest of checks will progress in parallel to this long running one. With my last commit the native tests `native-it` is already isolated from the rest of `install-it`, so they should run in parallel from the start and should not interfere with each other. Note that 2 hours is the maximum cap of timeouts. When successful they shouldn't take the full 2 hours but the actual time they need to finish (right now it's ~1h20m). That said, as I explained at https://github.com/apache/camel-k/issues/3715#issuecomment-1267922006, this is what it means to run Quarkus native build tests on GitHub-hosted runners. Right now, each native build test requires ~40 mins for a successful run and we already have 2 test cases, so it should take at least 80 mins. If we want to add more native tests the time will grow linearly. If we are not happy with it, either we should abandon the native tests from CI, or isolate the native tests into a dedicated workflow and put and run each test case with a separate job in the workflow. (The latter might be something we can consider in the future.) -- 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: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
