search

quarkusio / quarkus

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

[CI] - Kogito extension + Quarkus master #8694

Closed mariofusco closed 3 years ago

mariofusco commented 4 years ago

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

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

mariofusco commented 4 years ago

Build fixed:

mariofusco commented 4 years ago

Unfortunately, the build failed:

mariofusco commented 4 years ago

Build fixed:

mariofusco commented 4 years ago

Unfortunately, the build failed:

geoand commented 4 years ago

@mariofusco the break was a problem on our side. #9231 should take care of the problem

mariofusco commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@mariofusco I am seeing this:

2020-05-13T05:18:49.9015607Z [ERROR] [ERROR] Some problems were encountered while processing the POMs:
2020-05-13T05:18:49.9018861Z [ERROR] 'dependencies.dependency.version' for org.testcontainers:junit-jupiter:jar is missing. @ line 98, column 17

We recently removed org.testcontainers:junit-jupiter from our BOM, so I think you need to add it to yours

mariofusco commented 4 years ago

@geoand PR sent to kogito https://github.com/kiegroup/kogito-runtimes/pull/505 thanks for having reported this.

mariofusco commented 4 years ago

Build fixed:

mariofusco commented 4 years ago

Unfortunately, the build failed:

mariofusco commented 4 years ago

The build is still failing:

geoand commented 4 years ago

Seems like there was a connection timeout during dependency download.

@mariofusco would you perhaps consider doing something like https://github.com/quarkusio/quarkus-platform/pull/69 in order to avoid such failures in the future?

mariofusco commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@mariofusco can you take a look at my comment above? The build seems to have failed again due to dependency transfer issues

mariofusco commented 4 years ago

@geoand I can add those maven timeouts as you suggested but I'm afraid the problem is not (only) there. Now I tried to build locally our extension against latest quarkus master and I have a few tests failing. I'll investigate the problem and keep you updated.

geoand commented 4 years ago

Thanks @mariofusco

mariofusco commented 4 years ago

@geoand this pull request should fix both problems https://github.com/kiegroup/kogito-runtimes/pull/531 I'll keep you updated. Thanks for having reported it.

geoand commented 4 years ago

Coolio!

mariofusco commented 4 years ago

The build is still failing:

mariofusco commented 4 years ago

@geoand I merged that PR https://github.com/kiegroup/kogito-runtimes/commit/bbb83a58a8926bedd2c4f2366034f1de6b8abf4d Can you relaunch CI to check that everything is ok?

geoand commented 4 years ago

@mariofusco job restarted :)

mariofusco commented 4 years ago

Build fixed:

geoand commented 4 years ago

Thanks for addressing the issue @mariofusco!

mariofusco commented 4 years ago

Unfortunately, the build failed:

geoand commented 4 years ago

@mariofusco @evacchi something failed, but I can't really tell what. Can you have a look please?

Thanks

mariofusco commented 4 years ago

@geoand I gave a look at the log, but didn't find anything helpful. I think it's a CI failure, but really have no clue. For now I relaunched it and will keep an eye on it.

geoand commented 4 years ago

OK, cool

mariofusco commented 4 years ago

@geoand @evacchi it is confirmed it was a CI failure, I reran it and now it's green.

geoand commented 4 years ago

Great to know, thanks!

mariofusco commented 4 years ago

Build fixed:

mariofusco commented 4 years ago

Unfortunately, the build failed:

mariofusco commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@mariofusco @evacchi it seems like the kogito-quarkus-integration-test is failing

mariofusco commented 4 years ago

The build is still failing:

mariofusco commented 4 years ago

The build is still failing:

mariofusco commented 4 years ago

The build is still failing:

geoand commented 4 years ago

@mariofusco @evacchi the build is still failing, can you please take a look?

mariofusco commented 4 years ago

@geoand I ran our hot reload tests against latest quarkus snapshot and they all fail with the following message. Any hint on what could be going wrong?

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in io.quarkus.it.kogito.drools.HotReloadTest
[ERROR] io.quarkus.it.kogito.drools.HotReloadTest  Time elapsed: 0.004 s  <<< ERROR!
java.lang.ExceptionInInitializerError
        at io.quarkus.it.kogito.drools.HotReloadTest.<clinit>(HotReloadTest.java:39)
Caused by: java.lang.ClassCastException: class java.util.logging.LogManager$RootLogger cannot be cast to class org.jboss.logmanager.Logger (java.util.logging.LogManager$RootLogger is in module java.logging of loader 'bootstrap'; org.jboss.logmanager.Logger is in unnamed module of loader 'app')
        at io.quarkus.it.kogito.drools.HotReloadTest.<clinit>(HotReloadTest.java:39)
geoand commented 4 years ago

I don't, but I'm about to look into it

mariofusco commented 4 years ago

@geoand I'm pretty sure that the problem has been caused by this https://github.com/quarkusio/quarkus/commit/7a64dcd4d36afc8d59a0c4fe75a68152eddfdca8#

Do you agree? Should we import some specific logging impl?

geoand commented 4 years ago

@mariofusco here you go: https://github.com/kiegroup/kogito-runtimes/pull/600

geoand commented 4 years ago

@geoand I'm pretty sure that the problem has been caused by this 7a64dcd

Do you agree? Should we import some specific logging impl?

Yes, exactly, that's the problem

mariofusco commented 4 years ago

@mariofusco here you go: kiegroup/kogito-runtimes#600

yep, I confirm this fixed the problem, thanks a lot :)

geoand commented 4 years ago

You are welcome! And sorry we broke things on your side :(

evacchi commented 4 years ago

it would be helpful if it were possible to throw a self-explanatory message in case of bad config like: "You appear to have mis-configured your logger: please read https://quarkus.io/guides/logging#how-to-configure-logging-for-quarkustest". Thanks for helping @geoand !

geoand commented 4 years ago

@evacchi Yeah, that would indeed be useful!

mariofusco commented 4 years ago

Build fixed:

mariofusco commented 4 years ago

Unfortunately, the build failed:

mariofusco commented 4 years ago

Build fixed:

mariofusco commented 4 years ago

Unfortunately, the build failed: