-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Mutiny 2.6.2 and the Vert.x Mutiny bindings 3.13.2 #41860
Conversation
Thanks for your pull request! Your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
This comment has been minimized.
This comment has been minimized.
(rebased due to a an application BOM conflict) |
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
Status | Name | Step | Failures | Logs | Raw logs | Build scan |
---|---|---|---|---|---|---|
✔️ | JVM Tests - JDK 17 | Logs | Raw logs | 🔍 | ||
✖ | JVM Tests - JDK 21 | Build |
Logs | Raw logs | 🚧 |
You can consult the Develocity build scans.
Flaky tests - Develocity
⚙️ JVM Tests - JDK 17
📦 extensions/micrometer/deployment
✖ io.quarkus.micrometer.deployment.binder.VertxHttpClientMetricsTest.testWebClientMetrics
- History
event executor terminated
-java.util.concurrent.RejectedExecutionException
java.util.concurrent.RejectedExecutionException: event executor terminated
at io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:931)
at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:350)
at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:343)
at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:833)
at io.netty.util.concurrent.SingleThreadEventExecutor.execute0(SingleThreadEventExecutor.java:824)
at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:814)
at io.vertx.core.impl.EventLoopExecutor.execute(EventLoopExecutor.java:35)
📦 independent-projects/resteasy-reactive/server/vertx
✖ org.jboss.resteasy.reactive.server.vertx.test.sse.SseServerTestCase.shouldNotTryToSendToClosedSink
- History
1 expectation failed. Response body doesn't match expectation. Expected: "true" Actual: false
-java.lang.AssertionError
java.lang.AssertionError:
1 expectation failed.
Response body doesn't match expectation.
Expected: "true"
Actual: false
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
⚙️ Gradle Tests - JDK 17
📦 integration-tests/gradle
✖ io.quarkus.gradle.devmode.CustomWorkingDirDevModeTest.main
- History
Expecting actual: "hello" to contain: "from-custom-file"
-java.lang.AssertionError
java.lang.AssertionError:
Expecting actual:
"hello"
to contain:
"from-custom-file"
at app//io.quarkus.gradle.devmode.CustomWorkingDirDevModeTest.testDevMode(CustomWorkingDirDevModeTest.java:18)
at app//io.quarkus.gradle.devmode.QuarkusDevGradleTestBase.main(QuarkusDevGradleTestBase.java:60)
at java.base@17.0.11/java.lang.reflect.Method.invoke(Method.java:568)
I'm not sure what's going on with these builds being stuck. It's a bit concerning... |
I saw several of them blocking in Thread dump is:
|
Issue seems to be in this test:
that is a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the problem has anything to do with this particular PR so let's merge.
I created #41878 . |
Upgrade to: