Skip to content
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

Update to Vert.x 4.1.7 #22212

Merged
merged 1 commit into from
Dec 14, 2021
Merged

Conversation

cescoffier
Copy link
Member

@cescoffier cescoffier commented Dec 14, 2021

No description provided.

@quarkus-bot
Copy link

quarkus-bot bot commented Dec 14, 2021

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

  • title should preferably start with an uppercase character (if it makes sense!)

This message is automatically generated by a bot.

@cescoffier cescoffier changed the base branch from main to 2.2 December 14, 2021 16:32
@cescoffier cescoffier requested a review from gsmet December 14, 2021 16:32
@quarkus-bot quarkus-bot bot added area/amazon-lambda area/dependencies Pull requests that update a dependency file area/gradle Gradle area/jbang Issues related to when using jbang.dev with Quarkus area/maven labels Dec 14, 2021
@cescoffier cescoffier changed the title update to vertx 4.1.7 Update to vertx 4.1.7 Dec 14, 2021
@gsmet gsmet added this to the 2.2.4.Final milestone Dec 14, 2021
Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI hasn't started though.

@gsmet gsmet force-pushed the update-to-vertx-4.1.7 branch from d6c00fe to b1b8b2a Compare December 14, 2021 16:41
@gsmet
Copy link
Member

gsmet commented Dec 14, 2021

I force pushed to trigger CI. I don't know why but it happens a lot that 2.2 CI is not triggered if I don't push to it.

@gsmet gsmet changed the title Update to vertx 4.1.7 Update to Vert.x 4.1.7 Dec 14, 2021
@quarkus-bot
Copy link

quarkus-bot bot commented Dec 14, 2021

Failing Jobs - Building b1b8b2a

Status Name Step Failures Logs Raw logs
Gradle Tests - JDK 11 Windows Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.InjectQuarkusAppPropertiesDevModeTest.main line 19 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

io.quarkus.gradle.devmode.ModuleWithParentDependencyDevModeTest.main line 14 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

@gsmet gsmet merged commit 9ac4bad into quarkusio:2.2 Dec 14, 2021
@cescoffier cescoffier deleted the update-to-vertx-4.1.7 branch December 15, 2021 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/amazon-lambda area/dependencies Pull requests that update a dependency file area/gradle Gradle area/jbang Issues related to when using jbang.dev with Quarkus area/maven
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation is unclear about how to mount a PVC on Openshift Dev UI - Test report output not visible
2 participants