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

Bump flyway.version from 10.15.0 to 10.15.2 #41595

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 1, 2024

Bumps flyway.version from 10.15.0 to 10.15.2.
Updates org.flywaydb:flyway-core from 10.15.0 to 10.15.2

Release notes

Sourced from org.flywaydb:flyway-core's releases.

Flyway 10.15.2

See release notes here

CLI artifact available here

Flyway 10.15.1

See release notes here

CLI artifact available here

Commits

Updates org.flywaydb:flyway-sqlserver from 10.15.0 to 10.15.2

Updates org.flywaydb:flyway-mysql from 10.15.0 to 10.15.2

Updates org.flywaydb:flyway-database-oracle from 10.15.0 to 10.15.2

Updates org.flywaydb:flyway-database-postgresql from 10.15.0 to 10.15.2

Updates org.flywaydb:flyway-database-db2 from 10.15.0 to 10.15.2

Updates org.flywaydb:flyway-database-derby from 10.15.0 to 10.15.2

Updates org.flywaydb:flyway-database-mongodb from 10.15.0 to 10.15.2

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `flyway.version` from 10.15.0 to 10.15.2.

Updates `org.flywaydb:flyway-core` from 10.15.0 to 10.15.2
- [Release notes](https://github.com/flyway/flyway/releases)
- [Commits](flyway/flyway@flyway-10.15.0...flyway-10.15.2)

Updates `org.flywaydb:flyway-sqlserver` from 10.15.0 to 10.15.2

Updates `org.flywaydb:flyway-mysql` from 10.15.0 to 10.15.2

Updates `org.flywaydb:flyway-database-oracle` from 10.15.0 to 10.15.2

Updates `org.flywaydb:flyway-database-postgresql` from 10.15.0 to 10.15.2

Updates `org.flywaydb:flyway-database-db2` from 10.15.0 to 10.15.2

Updates `org.flywaydb:flyway-database-derby` from 10.15.0 to 10.15.2

Updates `org.flywaydb:flyway-database-mongodb` from 10.15.0 to 10.15.2

---
updated-dependencies:
- dependency-name: org.flywaydb:flyway-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-sqlserver
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-mysql
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-database-oracle
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-database-postgresql
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-database-db2
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-database-derby
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.flywaydb:flyway-database-mongodb
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the area/dependencies Pull requests that update a dependency file label Jul 1, 2024
Copy link

quarkus-bot bot commented Jul 2, 2024

Status for workflow Quarkus CI

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

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
✔️ Devtools Tests - JDK 17 Logs Raw logs 🔍
Devtools Tests - JDK 21 Build Failures Logs Raw logs 🔍
✔️ Devtools Tests - JDK 17 Windows Logs Raw logs 🔍
Native Tests - Data6 Build Failures Logs Raw logs 🔍
Native Tests - Security3 Build Failures Logs Raw logs 🔍

Full information is available in the Build summary check run.
You can consult the Develocity build scans.

Failures

⚙️ Devtools Tests - JDK 21 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

io.quarkus.devtools.codestarts.quarkus.ReactiveMessagingCodestartIT.buildKafka line 44 - History - More details - Source on GitHub

org.opentest4j.AssertionFailedError: 
[Run project return status is zero] 
expected: 0
 but was: 1
	at io.quarkus.devtools.testing.codestarts.QuarkusCodestartTest.buildProject(QuarkusCodestartTest.java:158)
	at io.quarkus.devtools.testing.codestarts.QuarkusCodestartTest.buildAllProjects(QuarkusCodestartTest.java:145)
	at io.quarkus.devtools.codestarts.quarkus.ReactiveMessagingCodestartIT.buildKafka(ReactiveMessagingCodestartIT.java:44)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

io.quarkus.devtools.codestarts.quarkus.ReactiveMessagingCodestartIT.buildKafka line 44 - History - More details - Source on GitHub

org.opentest4j.AssertionFailedError: 
[Run project return status is zero] 
expected: 0
 but was: 1
	at io.quarkus.devtools.testing.codestarts.QuarkusCodestartTest.buildProject(QuarkusCodestartTest.java:158)
	at io.quarkus.devtools.testing.codestarts.QuarkusCodestartTest.buildAllProjects(QuarkusCodestartTest.java:145)
	at io.quarkus.devtools.codestarts.quarkus.ReactiveMessagingCodestartIT.buildKafka(ReactiveMessagingCodestartIT.java:44)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

📦 integration-tests/devtools/target/quarkus-codestart-test/quarkus-messaging-kafka-9f7841dc-0e57-43a0-b89b-c105d59e2d55/real-data/java

ilove.quark.us.MyMessagingApplicationTest.test - History - More details - Source on GitHub

java.lang.RuntimeException: 
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.kafka.client.deployment.DevServicesKafkaProcessor#startKafkaDevService threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=docker.io/vectorized/redpanda:v24.1.2, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@39eb0323)
	at io.quarkus.kafka.client.deployment.DevServicesKafkaProcessor.startKafkaDevService(DevServicesKafkaProcessor.java:105)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:849)
	at io.quarkus.builder.BuildContext.run(BuildConte...

⚙️ Native Tests - Data6 #

- Failing: integration-tests/hibernate-search-orm-elasticsearch-tenancy 

📦 integration-tests/hibernate-search-orm-elasticsearch-tenancy

io.quarkus.it.hibernate.search.orm.elasticsearch.multitenancy.fruit.HibernateSearchTenancyFunctionalityInGraalITCase.test - History - More details - Source on GitHub

java.lang.RuntimeException: 
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor#launchDatabases threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=docker.io/postgres:14, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@ebd3689)
	at io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor.startDevDb(DevServicesDatasourceProcessor.java:362)
	at io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor.launchDatabases(DevServicesDatasourceProcessor.java:142)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeM...

⚙️ Native Tests - Security3 #

- Failing: integration-tests/security-webauthn 

📦 integration-tests/security-webauthn

io.quarkus.it.security.webauthn.test.NativeWebAuthnResourceIT.testWebAuthnUser - History - More details - Source on GitHub

java.lang.RuntimeException: 
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor#launchDatabases threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=docker.io/postgres:14, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@1cf75ee5)
	at io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor.startDevDb(DevServicesDatasourceProcessor.java:362)
	at io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor.launchDatabases(DevServicesDatasourceProcessor.java:142)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Native...

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 integration-tests/reactive-messaging-kafka

io.quarkus.it.kafka.KafkaConnectorTest.testFruits - History

  • Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <5> within 10 seconds. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <5> 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:1006)
	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
	at io.quarkus.it.kafka.KafkaConnectorTest.testFruits(KafkaConnectorTest.java:63)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

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.

Failures are due to Docker images not being downloaded.

@gsmet gsmet merged commit 7bb51b0 into main Jul 2, 2024
50 of 53 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.13 - main milestone Jul 2, 2024
@dependabot dependabot bot deleted the dependabot/maven/flyway.version-10.15.2 branch July 2, 2024 07:46
@gsmet gsmet modified the milestones: 3.13 - main, 3.12.1 Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant