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
So release-1.10.x is updated to Camel K runtime 1.15.1 while main remains with 1.14.0.
That means we will no longer be able to run native build tests with Quarkus 2.13.0 (Camel Catalog 1.15.x) or later. As soon as upgrading the runtime version used, we'll see the same failures with the main branch as well.
The text was updated successfully, but these errors were encountered:
That's exactly the reason why I opened: #3764. We will see likely the errors also against 1.16.0-SNAPSHOT then. Let's figure it out how to fix in main and release-1.10.x then.
Yes, I am aware of #3764. The exact reason why #3764 is failing at native-it is because of this issue.
And again, a simple fix of increasing timeout (40min -> 60min this time) seems to work #3774. I'll port #3774 to main as well as a short-term workaround.
Related to #3715.
I've been investigating why the native build E2E tests keep failing on
release-1.10.x
whereas they don't onmain
.https://github.com/apache/camel-k/actions/runs/3312246340/jobs/5468684587
I found that the key difference is the runtime versions used:
So
release-1.10.x
is updated to Camel K runtime 1.15.1 whilemain
remains with 1.14.0.That means we will no longer be able to run native build tests with Quarkus 2.13.0 (Camel Catalog 1.15.x) or later. As soon as upgrading the runtime version used, we'll see the same failures with the
main
branch as well.The text was updated successfully, but these errors were encountered: