Open domhanak opened 4 months ago
jstastny-cz
commented
4 months ago @domhanak did you try reproduce locally? From this report it seems it's CI-relevant issue, since you're providing Jenkins job as a reproducer, but I believe this is reproducible also on local - in which case it would be great to put mvn command there.
domhanak
commented
4 months ago @jstastny-cz yes I did, other than it freezing my laptop couple of times it worked, but didn't investigate. Not sure if the job was ever working after the migration, last success it looks to be Dec 6th. Needs to be taken care off, started this issue to track it.
There are some intermittent test failures that could be caused by environment issues.
7 test failures that repeat for past 10 builds ( Feb 16 for example.) however could be related to some changes.
The problem already mentioned above, again, could be misconfiguration or real issue.
I did a review of some available builds logs and logging it here: https://gist.github.com/domhanak/c99d8ec98e84dfee0f1d72053b208347
jstastny-cz
commented
4 months ago 2 different things IMHO, there are unstable tests. But the native compilation failure is fairly new after quarkus 3 upgrade.
Can you confirm that the native compilation error does not occur on your local? Also please note down mvn command used, it might be the difference to the CI environment.
domhanak
commented
4 months ago I used the same command that is used on CI, only difference is settings.xml.
[command] /usr/local/bin/mvn dependency:tree clean install -Dquickly -s /home/jenkins/workspace/KIE/kogito/main/nightly.native/kogito-apps.build-and-test@tmp/config13028030101733848056tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -BFocusing the issue on the one failure of building the module on CI, Once that is fixed, tests are next.
Currently, latest build fails because of different reason. Most probably this PR - https://github.com/apache/incubator-kie-kogito-runtimes/pull/3401 But just a guess.
Will check back later
pefernan
commented
4 months ago @domhanak yea, that PR affected the nightlies. It should be fixed as soon as we have new artifacts published.. If we cannot have them soon I'll send a PR to just adjust the extensions to use the old id's..
jstastny-cz
commented
4 months ago I used the same command that is used on CI, only difference is settings.xml.
[command] /usr/local/bin/mvn dependency:tree clean install -Dquickly -s /home/jenkins/workspace/KIE/kogito/main/nightly.native/kogito-apps.build-and-test@tmp/config13028030101733848056tmp -Dmaven.wagon.http.ssl.insecure=true -Dmaven.test.failure.ignore=true -nsu -ntp -fae -e -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.count=3 -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -BFocusing the issue on the one failure of building the module on CI, Once that is fixed, tests are next.
Currently, latest build fails because of different reason. Most probably this PR - apache/incubator-kie-kogito-runtimes#3401 But just a guess.
Will check back later
That's a different command, there's no native in there. This is probably a preceding mvn build of drools, runtimes, or so, but the actual kogito-apps native build should be later on.
domhanak
commented
4 months ago @domhanak yea, that PR affected the nightlies. It should be fixed as soon as we have new artifacts published.. If we cannot have them soon I'll send a PR to just adjust the extensions to use the old id's..
No worries, handle it as planned on your issue.
@jstastny-cz yea, so it passed because I forgot to check the command I run locally the second time. Issues between keyboard and chair solved :heavy_check_mark: and the build failure is reproducible locally.
I am trying with following properties as per - https://github.com/quarkusio/quarkus/issues/26835
-Dquarkus.native.additional-build-args="--initialize-at-run-time=org.apache.kafka.common.security.authenticator.SaslClientAuthenticator"and get back with results
Describe the bug
Nightly native build job of kogito-apps [1] fails consistently for past week.
The failure i caused by
data-audit-quarkus-jpa-serviceproject. Relevant output from logs:[1] https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/nightly.native/job/kogito-apps.build-and-test/
Expected behavior
The job will be passing and no test failures: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/nightly.native/job/kogito-apps.build-and-test/lastCompletedBuild/testReport/
Actual behavior
Job si failing and there are test failures. https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/nightly.native/job/kogito-apps.build-and-test/lastCompletedBuild/testReport/
How to Reproduce?
Execute https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/nightly.native/job/kogito-apps.build-and-test/
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response