search

quarkusio / quarkus

Quarkus: Supersonic Subatomic Java.
https://quarkus.io
Apache License 2.0
13.35k stars 2.56k forks source link

[CI] - Cassandra extension + Quarkus main #9183

Open absurdfarce opened 4 years ago

absurdfarce commented 4 years ago

This issue will be open and closed dependent on the state of https://github.com/datastax/cassandra-quarkus building against Quarkus master snapshot.

If you have interest in being notified of this subscribe to the issue.

absurdfarce commented 4 years ago

The build is still failing:

adutra commented 4 years ago

I fixed the issue, it was an XML formatting problem.

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

Build fixed:

absurdfarce commented 4 years ago

Unfortunately, the build failed:

adutra commented 4 years ago

Unfortunately I think the build will keep failing as long as we reference driver 4.7.0-SNAPSHOT:

2020-06-05T05:19:09.4557688Z [ERROR] The build could not read 5 projects -> [Help 1]
2020-06-05T05:19:09.4561177Z [ERROR]   
2020-06-05T05:19:09.4574063Z [ERROR]   The project com.datastax.oss.quarkus:cassandra-quarkus-bom:1.0.0-SNAPSHOT (/home/runner/work/cassandra-quarkus/cassandra-quarkus/current-repo/bom-runtime/pom.xml) has 1 error
2020-06-05T05:19:09.4582990Z [ERROR]     Non-resolvable import POM: Could not find artifact com.datastax.oss:java-driver-bom:pom:4.7.0-SNAPSHOT in snapshots-repo (https://oss.sonatype.org/content/repositories/snapshots) @ line 40, column 19 -> [Help 2]
absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

absurdfarce commented 4 years ago

The build is still failing:

adutra commented 4 years ago

Fixed. The quickstart module was still referencing driver 4.7.0-SNAPSHOT.

absurdfarce commented 4 years ago

Build fixed:

absurdfarce commented 4 years ago

Unfortunately, the build failed:

adutra commented 4 years ago

This is indeed unfortunate but it doesn't seem to be our fault but rather network problems for the last 2 failed builds.

Last build error:

2020-06-23T05:43:27.0153281Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) on project cassandra-quarkus-quickstart: Execution default-install of goal org.apache.maven.plugins:maven-install-plugin:2.4:install failed: Plugin org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-install-plugin:jar:2.4 -> org.codehaus.plexus:plexus-utils:jar:3.0.5: Failed to read artifact descriptor for org.codehaus.plexus:plexus-utils:jar:3.0.5: Could not transfer artifact org.codehaus.plexus:plexus-utils:pom:3.0.5 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.5/plexus-utils-3.0.5.pom: Connection timed out (Read failed) -> [Help 1]

@gsmet do you know what's going on or how to fix this?

Builds dashboard: https://github.com/datastax/cassandra-quarkus/actions?query=workflow%3A%22Quarkus+ecosystem+CI%22

absurdfarce commented 4 years ago

Build fixed:

absurdfarce commented 4 years ago

Unfortunately, the build failed:

absurdfarce commented 4 years ago

The build is still failing:

adutra commented 4 years ago

I had the fix yesterday and forgot to push :-D

absurdfarce commented 4 years ago

Build fixed:

absurdfarce commented 4 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

The build is still failing:

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

The build is still failing:

adutra commented 3 years ago

Well, Mutiny 0.6.0 just introduced a breaking change in a minor version :-/; they added one more method:

https://smallrye.io/smallrye-mutiny/apidocs/io/smallrye/mutiny/Multi.html#onSubscribe--

The change was introduced by https://github.com/smallrye/smallrye-mutiny/pull/195.

I think we don't have any choice. The build will keep failing until they release a new Quarkus version with Mutiny 0.6.0, then we will be able to update our impls.

absurdfarce commented 3 years ago

The build is still failing:

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Unfortunately, the build failed:

absurdfarce commented 3 years ago

The build is still failing:

gsmet commented 3 years ago

@absurdfarce @adutra I'm a bit worried about the failure. Could you have a look? I wonder if it's an issue with the driver or something we broke in Quarkus.

absurdfarce commented 3 years ago

@gsmet There haven't been any commits to the cassandra-quarkus repo in August so I don't think it's coming from our side.

That test sets the Netty event loop for the Java driver to whatever it gets from Quarkus. That's accessed via the following bit of code:

  public void setInjectedNettyEventLoop(boolean useQuarkusNettyEventLoop) {
    CassandraClientProducer producer = getProducerInstance();

    if (useQuarkusNettyEventLoop) {
      EventLoopGroup mainEventLoop =
          Arc.container()
              .instance(EventLoopGroup.class, new AnnotationLiteral<MainEventLoopGroup>() {})
              .get();

      producer.setMainEventLoop(mainEventLoop);
    }
  }

It then just runs a query (presumably using that event loop) and checks to see whether the name of the thread that ran the query matches up to io.vertx.core.impl.VertxThread.

Any of that ring a bell for you?

gsmet commented 3 years ago

Not really. @stuartwdouglas does it ring a bell?

absurdfarce commented 3 years ago

Build fixed:

absurdfarce commented 3 years ago

Was there a specific change that resolved the last build failure?

gsmet commented 3 years ago

No. We didn't change a thing (which worries me a bit tbh).