quarkusio / quarkus

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

[CI] - Quarkus Platform + Quarkus main #8593

Open quarkusbot opened 4 years ago

quarkusbot commented 4 years ago

Issue will be reopened when https://github.com/quarkusio/quarkus-platform fails to build against latest Quarkus Snapshots.

quarkusbot commented 4 years ago

Build fixed:

quarkusbot commented 4 years ago

Unfortunately, the build failed:

geoand commented 4 years ago

@lburgazzoli seems like a change in io.quarkus.undertow.runtime.UndertowDeploymentRecorder broke one of your tests:

2020-04-17T05:15:50.7886790Z [ERROR] Tests run: 8, Failures: 0, Errors: 1, Skipped: 7, Time elapsed: 7.012 s <<< FAILURE! - in org.apache.camel.quarkus.component.http.it.HttpTest
2020-04-17T05:15:50.7893583Z [ERROR] httpsProducer{String}[1]  Time elapsed: 0.015 s  <<< ERROR!
2020-04-17T05:15:50.7896073Z java.lang.RuntimeException: 
2020-04-17T05:15:50.7902667Z java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
2020-04-17T05:15:50.7941738Z    [error]: Build step io.quarkus.undertow.deployment.UndertowBuildStep#build threw an exception: java.lang.NoSuchMethodError: 'io.quarkus.runtime.RuntimeValue io.quarkus.undertow.runtime.UndertowDeploymentRecorder.createDeployment(java.lang.String, java.util.Set, java.util.Set, io.quarkus.runtime.LaunchMode, io.quarkus.runtime.ShutdownContext, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)'
lburgazzoli commented 4 years ago

The error seems related to a different deepndency used ? because it is thrown by a quarkus build item

geoand commented 4 years ago

Hm... You are right... I'll look into it

lburgazzoli commented 4 years ago

guess the -deployment dependencies chain is from the camel deps whereas the runtime is from the platform

geoand commented 4 years ago

Most likely something like that

gsmet commented 4 years ago

/cc @ppalaga as he already debugged a similar issue that led to a fix by @aloubyansky

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

The build is still failing:

galderz commented 4 years ago

The build is still failing:

I've came across this issue too: https://github.com/apache/camel-quarkus/issues/1115

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

Build fixed:

quarkusbot commented 4 years ago

Unfortunately, the build failed:

geoand commented 4 years ago

Should be fixed by https://github.com/quarkusio/quarkus-platform/pull/65

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@gsmet guess what happened...

Camel broke because of the DataSource change...

java.lang.RuntimeException: java.lang.NoClassDefFoundError: io/quarkus/agroal/runtime/AbstractDataSourceProducer
geoand commented 4 years ago

Although looking at the code it doesn't seem like AbstractDataSourceProducer is being used anywhere by Camel.

lburgazzoli commented 4 years ago

We do get the datasource through CDI, i.e. we configure quarkus datasource then we retrieve it in our jdbc component

geoand commented 4 years ago

@lburgazzoli can you point me to the code that retrieves the datasource?

lburgazzoli commented 4 years ago

I did test quarkus master against camel and it does not fail for me so it looks like there's a wrong dependency pulled in

@quarkusio/devtools @gsmet

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

The build is still failing:

geoand commented 4 years ago

The latest failure should be fixed by #9231

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

The build is still failing:

geoand commented 4 years ago

Failure seems like a network issue:

2020-05-14T05:45:24.5788818Z [ERROR] Failed to execute goal on project quarkus-universe-integration-tests-camel-netty: Could not resolve dependencies for project io.quarkus:quarkus-universe-integration-tests-camel-netty:jar:999-SNAPSHOT: Could not transfer artifact org.apache.camel.quarkus:camel-quarkus-integration-test-netty:jar:1.0.0-M7 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/apache/camel/quarkus/camel-quarkus-integration-test-netty/1.0.0-M7/camel-quarkus-integration-test-netty-1.0.0-M7.jar: Connection timed out (Read failed) -> [Help 1]
ppalaga commented 4 years ago

@geoand https://github.com/quarkusio/quarkus-platform/pull/69 might help

quarkusbot commented 4 years ago

Build fixed:

quarkusbot commented 4 years ago

Unfortunately, the build failed:

geoand commented 4 years ago

ActiveMQ test from Camel seems to be failing @ppalaga

2020-05-18T05:17:31.5433480Z [INFO] Running org.apache.camel.quarkus.component.activemq.it.ActiveMQTest
2020-05-18T05:17:32.2424372Z [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.688 s <<< FAILURE! - in org.apache.camel.quarkus.component.activemq.it.ActiveMQTest
2020-05-18T05:17:32.2430070Z [ERROR] testActiveMQComponent  Time elapsed: 0.023 s  <<< ERROR!
2020-05-18T05:17:32.2442928Z java.lang.RuntimeException: io.quarkus.bootstrap.BootstrapException: Failed to create the application model for io.quarkus:quarkus-universe-integration-tests-camel-activemq::jar:999-SNAPSHOT
galderz commented 4 years ago

Please note that there might more hidden failures because there are some native tests that are not being run by CI, e.g. camel w/ jira. And no, mockito tests are not enough here. More info in https://github.com/apache/camel-quarkus/issues/1166

quarkusbot commented 4 years ago

The build is still failing:

quarkusbot commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@ppalaga any idea what this failure is all about?

2020-05-22T06:50:37.7670775Z [INFO] Running org.apache.camel.quarkus.component.activemq.it.ActiveMQTest
2020-05-22T06:50:38.5623577Z [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.779 s <<< FAILURE! - in org.apache.camel.quarkus.component.activemq.it.ActiveMQTest
2020-05-22T06:50:38.5626840Z [ERROR] testActiveMQComponent  Time elapsed: 0.016 s  <<< ERROR!
2020-05-22T06:50:38.5633711Z java.lang.RuntimeException: io.quarkus.bootstrap.BootstrapException: Failed to create the application model for io.quarkus:quarkus-universe-integration-tests-camel-activemq::jar:999-SNAPSHOT
lburgazzoli commented 4 years ago

@geoand I think this exception need to be more detailed about the root cause of the issue, it is not the first time I see it and every time it puzzles me as it can be anything @ppalaga can you have a look ?

geoand commented 4 years ago

@geoand I think this exception need to be more detailed about the root cause of the issue, it is not the first time I see it and every time it puzzles me as it can be anything

Indeed yes

ppalaga commented 4 years ago

It looks like a variant of https://github.com/quarkusio/quarkus/issues/9299 I guess adding a dummy class or resource under ''src/main` of the platform test module could help.

quarkusbot commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@ppalaga have you perhaps opened a PR with your previous suggestion?

ppalaga commented 4 years ago

I can try to.

At the same time, having a proper fix for https://github.com/quarkusio/quarkus/issues/9299 would be much more welcome, where I might try to have a look too, unless somebody from Quarkus steps in.

quarkusbot commented 4 years ago

The build is still failing:

ppalaga commented 4 years ago

Update: I do not plan to implement the workaround anymore. There is https://github.com/quarkusio/quarkus/pull/9582 that contains a fix for the underlying issue. Hopefully it gets merged soon.

geoand commented 4 years ago

Makes sense

quarkusbot commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@ppalaga tests are still failing even with https://github.com/quarkusio/quarkus/pull/9582 merged:

2020-05-27T05:19:21.9944372Z [INFO] Running org.apache.camel.quarkus.component.activemq.it.ActiveMQTest
2020-05-27T05:19:22.6673516Z [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.656 s <<< FAILURE! - in org.apache.camel.quarkus.component.activemq.it.ActiveMQTest
2020-05-27T05:19:22.6677863Z [ERROR] testActiveMQComponent  Time elapsed: 0.016 s  <<< ERROR!
2020-05-27T05:19:22.6687914Z java.lang.RuntimeException: io.quarkus.bootstrap.BootstrapException: Failed to create the applic
aloubyansky commented 4 years ago

@gsmet notified me this morning that the NoSrc* devmode tests were failing and it's easily reproducible with master by removing ~/.m2/repository/io/quarkus/quarkus-integration-test-devmode/ and re-running integration-tests/dev-mode. The test is trying to resolve the project's artifact and while it is discovering its pom.xml in the workspace, it is failing to resolve as the JAR, given that that is its packaging type. The issue is that it has neither classes nor resources, it hasn't yet been packaged (Maven would produce an empty JAR) and of course hasn't been installed. So there is no valid path to associate with the artifact. Theoretically, we could create an empty classes dir but it is not safe at the time we are given a chance to resolve the path locally.

aloubyansky commented 4 years ago

One option would be to check if the project contains sources and/or resources directories and if it does not, consider it having no content and simply create an empty classes dir for it (given that it's supposed to be a JAR). However, during the packaging phase a plugin can be configured to customize the manifest and/or generate extra content to be included into the JAR. If that JAR is already available in the local repo, our tests won't be picking it up. If I actually do this trick for these tests, they fail with

Caused by: java.lang.ClassCastException: class io.quarkus.bootstrap.app.CuratedApplication cannot be cast to class io.quarkus.bootstrap.app.CuratedApplication (io.quarkus.bootstrap.app.CuratedApplication is in unnamed module of loader 'app'; io.quarkus.bootstrap.app.CuratedApplication is in unnamed module of loader io.quarkus.bootstrap.classloading.QuarkusClassLoader @7051777c)
    at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:41)
    at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:131)

which is intriguing.