Do not contaminate dev services with config from other dev services#53794
Open
gsmet wants to merge 1 commit intoquarkusio:mainfrom
Open
Do not contaminate dev services with config from other dev services#53794gsmet wants to merge 1 commit intoquarkusio:mainfrom
gsmet wants to merge 1 commit intoquarkusio:mainfrom
Conversation
We use to push all the config collected for all dev services to RunningService but we should limit it to the config of the current dev service.
Status for workflow
|
| Status | Name | Step | Failures | Logs | Raw logs | Build scan |
|---|---|---|---|---|---|---|
| ✔️ | Kubernetes Tests - JDK 25 | Logs | Raw logs | 🔍 | ||
| ✔️ | Kubernetes Tests - JDK 25 Semeru | Logs | Raw logs | 🔍 | ||
| ❌ | Kubernetes Tests - JDK 17 Windows | Download previously uploaded .m2 content |
Logs | Raw logs | 🚧 |
You can consult the Develocity build scans.
Flaky tests - Develocity
⚙️ JVM Tests - JDK 17
📦 extensions/quartz/deployment
❌ io.quarkus.quartz.test.PausedSchedulerTest.testSchedulerPauseResume - History
expected: <false> but was: <true>-org.opentest4j.AssertionFailedError
Details
org.opentest4j.AssertionFailedError: expected: <false> but was: <true>
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:158)
at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:139)
at org.junit.jupiter.api.AssertFalse.failNotFalse(AssertFalse.java:69)
at org.junit.jupiter.api.AssertFalse.assertFalse(AssertFalse.java:41)
at org.junit.jupiter.api.AssertFalse.assertFalse(AssertFalse.java:35)
at org.junit.jupiter.api.Assertions.assertFalse(Assertions.java:246)
at io.quarkus.quartz.test.PausedSchedulerTest.testSchedulerPauseResume(PausedSchedulerTest.java:47)
⚙️ Maven Tests - JDK 25 Semeru
📦 integration-tests/maven
❌ io.quarkus.maven.it.QuestionMarkInPathIntegrationTestIT.testLegacyJar - History
Expecting actual: "Apr 24, 2026 7:43:07 PM org.jboss.logmanager.JBossLoggerFinder getLogger ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected. pom.xml-java.lang.AssertionError
Details
java.lang.AssertionError:
Expecting actual:
"Apr 24, 2026 7:43:07 PM org.jboss.logmanager.JBossLoggerFinder getLogger
ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected.
pom.xml
[INFO] ------------------------------[ quarkus ]-------------------------------
[INFO]
❌ io.quarkus.maven.it.QuestionMarkInPathIntegrationTestIT.testLegacyJar - History
Expecting actual: "Apr 24, 2026 7:43:07 PM org.jboss.logmanager.JBossLoggerFinder getLogger ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected. pom.xml-java.lang.AssertionError
Details
java.lang.AssertionError:
Expecting actual:
"Apr 24, 2026 7:43:07 PM org.jboss.logmanager.JBossLoggerFinder getLogger
ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected.
pom.xml
[INFO] ------------------------------[ quarkus ]-------------------------------
[INFO]
⚙️ Native Tests - Messaging1
📦 integration-tests/reactive-messaging-kafka
❌ io.quarkus.it.kafka.KafkaConnectorIT.testPets - History
Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <3> within 10 seconds.-org.awaitility.core.ConditionTimeoutException
Details
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <3> within 10 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
at io.quarkus.it.kafka.KafkaConnectorTest.testPets(KafkaConnectorTest.java:62)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
⚙️ JVM Integration Tests - JDK 21
📦 integration-tests/reactive-messaging-kafka
❌ io.quarkus.it.kafka.KafkaConnectorTest.testPrices - History
Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <7> but was: <6> within 10 seconds.-org.awaitility.core.ConditionTimeoutException
Details
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <7> but was: <6> within 10 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
at io.quarkus.it.kafka.KafkaConnectorTest.testPrices(KafkaConnectorTest.java:77)
Caused by: org.opentest4j.AssertionFailedError: expected: <7> but was: <6>
⚙️ JVM Integration Tests - JDK 25 Semeru
📦 integration-tests/reactive-messaging-kafka
❌ io.quarkus.it.kafka.KafkaConnectorTest.testPets - History
Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <0> but was: <3> within 10 seconds.-org.awaitility.core.ConditionTimeoutException
Details
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <0> but was: <3> within 10 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
at io.quarkus.it.kafka.KafkaConnectorTest.testPets(KafkaConnectorTest.java:62)
Caused by: org.opentest4j.AssertionFailedError: expected: <0> but was: <3>
Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <3> within 10 seconds.-org.awaitility.core.ConditionTimeoutException
Details
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <3> within 10 seconds.
at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
at io.quarkus.it.kafka.KafkaConnectorTest.testPets(KafkaConnectorTest.java:62)
Caused by: org.opentest4j.AssertionFailedError: expected: <6> but was: <3>
❌ io.quarkus.it.kafka.KafkaConnectorTest.testRequestReply - History
iterable contents differ at index [0], expected: <reply-1> but was: <{"details":"Error id 2d65be98-38bd-4b11-900a-a82dac58747c-1, org.jboss.resteasy.spi.UnhandledException: io.smallrye.reactive.messaging.kafka.reply.KafkaRequestReplyTimeoutException: Timeout waiting for a reply for request with correlation ID: 7d30b65c-09a9-4945-855b-42f4cc2347d6","stack":"org.jboss.resteasy.spi.UnhandledException: io.smallrye.reactive.messaging.kafka.reply.KafkaRequestReplyTimeoutException: Timeout waiting for a reply for request with correlation ID: 7d30b65c-09a9-4945-855b-42f4cc2347d6\n\tat org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:107)\n\tat org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:344)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:205)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:452)\n\tat org.jboss.resteasy.core.Synchron...-org.opentest4j.AssertionFailedError
Details
org.opentest4j.AssertionFailedError: iterable contents differ at index [0], expected: <reply-1> but was: <{"details":"Error id 2d65be98-38bd-4b11-900a-a82dac58747c-1, org.jboss.resteasy.spi.UnhandledException: io.smallrye.reactive.messaging.kafka.reply.KafkaRequestReplyTimeoutException: Timeout waiting for a reply for request with correlation ID: 7d30b65c-09a9-4945-855b-42f4cc2347d6","stack":"org.jboss.resteasy.spi.UnhandledException: io.smallrye.reactive.messaging.kafka.reply.KafkaRequestReplyTimeoutException: Timeout waiting for a reply for request with correlation ID: 7d30b65c-09a9-4945-855b-42f4cc2347d6\n\tat org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:107)\n\tat org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:344)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:205)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:452)\n...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We use to push all the config collected for all dev services to RunningService but we should limit it to the config of the current dev service.
Created as draft as it needs a full CI run.