Skip to content

Conversation

metacosm
Copy link
Contributor

@metacosm metacosm commented May 9, 2025

This updates the dependencies used in Kubernetes integration tests to more recent versions. Note that there doesn't seem to be a real recent, tagged version of OCP to use, at least, not that I could quickly figure out, without going hunting for it, so this might require some more work.

@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label May 9, 2025

This comment was marked as resolved.

@geoand geoand changed the title Update to more recent versions Update CI to use more recent versions of Kubernetes in the relevant jobs May 9, 2025
@gastaldi
Copy link
Contributor

gastaldi commented May 9, 2025

Can't merge this, need an admin to do it

@geoand
Copy link
Contributor

geoand commented May 9, 2025

CI seems stuck

@manusa
Copy link
Contributor

manusa commented May 10, 2025

Openshift won't work.
The runner only admits 3.x.
The runner requires Ubuntu 20 which is no longer provided by GitHub.
This job needs to be removed or run on a hosted runner with the required OS.

@metacosm
Copy link
Contributor Author

Openshift won't work. The runner only admits 3.x. The runner requires Ubuntu 29 which is no longer provided by GitHub. This job needs to be removed or run on a hosted runner with the required OS.

This brings the question as to whether this is indeed even worth testing on OpenShift if we can't check current versions. What do you think, @gsmet?

@metacosm
Copy link
Contributor Author

Why can't I even check what's going on with the CI Sanity Check?

@geoand
Copy link
Contributor

geoand commented May 12, 2025

Something seems to be stuck. I propose a rebase and force push

@metacosm metacosm force-pushed the update-versions branch 2 times, most recently from 69d3e54 to 8cf8511 Compare May 12, 2025 12:11
@metacosm
Copy link
Contributor Author

Something seems to be stuck. I propose a rebase and force push

Doesn't seem to be doing anything.

@geoand
Copy link
Contributor

geoand commented May 12, 2025

No idea what the issue is

@gsmet
Copy link
Member

gsmet commented May 12, 2025

It won't run CI as it's touching something that is not relevant to main CI.

IIRC, this is only triggered with a schedule.

@gsmet
Copy link
Member

gsmet commented May 12, 2025

And my understanding was that we were unable to test with recent OpenShift and that these workflows were kinda outdated (I raised the problem a while ago).

@gastaldi
Copy link
Contributor

We still have IBM Cloud to perform these tests. I can set up a cluster with the latest OpenShift version if necessary

@metacosm
Copy link
Contributor Author

What's the resolution on this? It would be good to start getting at plain Kube CI runs again…

OpenShift-related versions cannot be updated at this point.

This comment has been minimized.

Copy link

quarkus-bot bot commented Jun 27, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 69682f1.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.


Flaky tests - Develocity

⚙️ Maven Tests - JDK 17

📦 integration-tests/devmode

io.quarkus.test.devui.DevUIGrpcSmokeTest.testTestService - History

  • Too many recursions, message not returned for id [1603571926] - java.lang.RuntimeException
java.lang.RuntimeException: Too many recursions, message not returned for id [1603571926]
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:168)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:171)

⚙️ JVM Integration Tests - JDK 17

📦 integration-tests/opentelemetry-grpc-only

io.quarkus.it.opentelemetry.grpc.HelloGrpcClientTest.testHello - History

  • java.lang.RuntimeException: Failed to start quarkus - java.lang.RuntimeException
java.lang.RuntimeException: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:668)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:763)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)

⚙️ JVM Integration Tests - JDK 17 Windows

📦 integration-tests/grpc-hibernate

com.example.grpc.hibernate.VertxBlockingRawTest.shouldAdd - History

  • Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at com.example.grpc.hibernate.BlockingRawTestBase.shouldAdd(BlockingRawTestBase.java:59)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)

⚙️ JVM Integration Tests - JDK 21

📦 integration-tests/opentelemetry-grpc-only

io.quarkus.it.opentelemetry.grpc.HelloGrpcClientTest.testHello - History

  • java.lang.RuntimeException: Failed to start quarkus - java.lang.RuntimeException
java.lang.RuntimeException: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:668)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:763)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Caused by: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)

@geoand geoand merged commit ab90e24 into quarkusio:main Jun 27, 2025
57 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.25 - main milestone Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure triage/flaky-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants