You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/10/26 04:43:37 UTC
[GitHub] [camel-k] tadayosi opened a new issue, #3777: E2E - Isolate native tests into a dedicated workflow and put each test with a separate job in the workflow
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi closed issue #3777: E2E - Isolate native tests into a dedicated workflow and put each test with a separate job in the workflow
Posted by GitBox <gi...@apache.org>.
tadayosi closed issue #3777: E2E - Isolate native tests into a dedicated workflow and put each test with a separate job in the workflow
URL: https://github.com/apache/camel-k/issues/3777
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3777: E2E - Isolate native tests into a dedicated workflow and put each test with a separate job in the workflow
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3777:
URL: https://github.com/apache/camel-k/issues/3777#issuecomment-1345971155
It's already done.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3777: E2E - Isolate native tests into a dedicated workflow and put each test with a separate job in the workflow
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3777:
URL: https://github.com/apache/camel-k/issues/3777#issuecomment-1291634113
> 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.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3777: E2E - Isolate native tests into a dedicated workflow and put each test with a separate job in the workflow
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3777:
URL: https://github.com/apache/camel-k/issues/3777#issuecomment-1293006935
Wow, the tests have passed but already close to the timeout 60m. It's a good reason to separate the native tests soon.
https://github.com/apache/camel-k/actions/runs/3329377626/jobs/5506518141
```
📦 github.com/apache/camel-k/e2e/namespace/native
✅ TestNativeBinding (57m18.75s)
✅ TestNativeBinding/kamelet_binding_with_native_build (55m34.35s)
✅ TestNativeBinding/warm_up_before_native_build_testing (1m29.93s)
✅ TestNativeIntegrations (54m30.12s)
✅ TestNativeIntegrations/automatic_rollout_deployment_from_fast-jar_to_native_kit (52m47.04s)
✅ TestNativeIntegrations/unsupported_integration_source_language (860ms)
✅ TestNativeIntegrations/warm_up_before_native_build_testing (1m27.35s)
```
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org