You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 #3715 (comment), 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.)
The text was updated successfully, but these errors were encountered:
An alternative could be to have a separated check that run on a nightly basis instead (we can even put beside the nightly releases to force us to look to it when failures happen). We will still have a feedback on early failures, but it won't affect that much the time to build at each PR.
#3774 (comment)
With my last commit the native tests
native-it
is already isolated from the rest ofinstall-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 #3715 (comment), 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.)
The text was updated successfully, but these errors were encountered: