-
Notifications
You must be signed in to change notification settings - Fork 209
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
Quarkus 3: update patches #3168
Conversation
jenkins rewrite quarkus-3 |
(tests) - kogito-runtimes job Reproducerexport BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Test results:
Those are the test failures: org.kie.kogito.persistence.kafka.KafkaProcessInstancesIT.testFindByIdReadModeexpected: 5 but was: 0 |
(tests) - kogito-runtimes job Reproducerexport BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Test results:
Those are the test failures: org.kie.kogito.tracing.QuarkusTracingAddonDevServicesIT.testEvaluateLoanEligibilityjava.lang.RuntimeException: Failed to start quarkus |
jenkins rewrite quarkus-3 |
Rewrite quarkus-3 before.sh patch file job Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest.quarkus-3/job/kogito-runtimes.rewrite/17/display/redirect Console Logs[2023-08-09T11:16:10.659Z] hint: You can replace "git config" with "git config --global" to set a default[2023-08-09T11:16:10.659Z] hint: preference for all repositories. You can also pass --rebase, --no-rebase, [2023-08-09T11:16:10.659Z] hint: or --ff-only on the command line to override the configured default per [2023-08-09T11:16:10.659Z] hint: invocation. [2023-08-09T11:16:10.659Z] fatal: Need to specify how to reconcile divergent branches. [Pipeline] } [Pipeline] // withCredentials [Pipeline] echo [2023-08-09T11:16:10.730Z] [2023-08-09T11:16:10.730Z] ------------------------------------------------------------- [2023-08-09T11:16:10.730Z] [ERROR] Can't merge source into Target. Please rebase PR branch. [2023-08-09T11:16:10.730Z] ------------------------------------------------------------- [2023-08-09T11:16:10.730Z] Source: git://github.com/radtriste/drools quarkus-3-fix [2023-08-09T11:16:10.730Z] Target: 8972331416 KOGITO-5386: added a new parameter for unique branch name (#5455) [2023-08-09T11:16:10.730Z] ------------------------------------------------------------- [2023-08-09T11:16:10.730Z] [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Generate rewrite patch) Stage "Generate rewrite patch" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Push changes) Stage "Push changes" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] script [Pipeline] { [Pipeline] cleanWs [2023-08-09T11:16:11.184Z] [WS-CLEANUP] Deleting project workspace... [2023-08-09T11:16:11.184Z] [WS-CLEANUP] Deferred wipeout is used... [2023-08-09T11:16:11.189Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // script [Pipeline] script [Pipeline] { [Pipeline] sh [2023-08-09T11:16:11.636Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest.quarkus-3/job/kogito-runtimes.rewrite/17/api/json [Pipeline] readJSON [Pipeline] sh |
jenkins rewrite quarkus-3 |
jenkins rewrite quarkus-3 |
Rewrite quarkus-3 before.sh patch file job Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest.quarkus-3/job/kogito-runtimes.rewrite/19/display/redirect Console Logs[2023-08-09T12:16:06.018Z] hint: You can replace "git config" with "git config --global" to set a default[2023-08-09T12:16:06.018Z] hint: preference for all repositories. You can also pass --rebase, --no-rebase, [2023-08-09T12:16:06.018Z] hint: or --ff-only on the command line to override the configured default per [2023-08-09T12:16:06.018Z] hint: invocation. [2023-08-09T12:16:06.018Z] fatal: Need to specify how to reconcile divergent branches. [Pipeline] } [Pipeline] // withCredentials [Pipeline] echo [2023-08-09T12:16:06.088Z] [2023-08-09T12:16:06.088Z] ------------------------------------------------------------- [2023-08-09T12:16:06.088Z] [ERROR] Can't merge source into Target. Please rebase PR branch. [2023-08-09T12:16:06.088Z] ------------------------------------------------------------- [2023-08-09T12:16:06.088Z] Source: git://github.com/radtriste/drools quarkus-3-fix [2023-08-09T12:16:06.088Z] Target: fb7e4da7ce [DROOLS-7522] Alyways use AbstractLeftTuple instead of LeftTuple (Fix the secondary super cache problem in Drools) (#5443) [2023-08-09T12:16:06.088Z] ------------------------------------------------------------- [2023-08-09T12:16:06.088Z] [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Generate rewrite patch) Stage "Generate rewrite patch" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Push changes) Stage "Push changes" skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] script [Pipeline] { [Pipeline] cleanWs [2023-08-09T12:16:06.604Z] [WS-CLEANUP] Deleting project workspace... [2023-08-09T12:16:06.604Z] [WS-CLEANUP] Deferred wipeout is used... [2023-08-09T12:16:06.613Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // script [Pipeline] script [Pipeline] { [Pipeline] sh [2023-08-09T12:16:07.040Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest.quarkus-3/job/kogito-runtimes.rewrite/19/api/json [Pipeline] readJSON [Pipeline] sh |
jenkins rewrite quarkus-3 |
jenkins run quarkus-3 |
(quarkus-3) - kogito-runtimes job Reproducerexport BUILD_MVN_OPTS_CURRENT=-T 1C NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Test results:
Those are the test failures: org.kie.kogito.persistence.kafka.KafkaProcessInstancesIT.testFindByIdReadModeexpected: 5 but was: 0 org.kie.kogito.integrationtests.springboot.OASTest.testOASisValidExpecting empty but was: ["Unable to read location `http://localhost:43827/v3/api-docs`"] org.kie.kogito.integrationtests.springboot.OASTest.testOASisSwaggerUICompatibleExpecting empty but was: ["Unable to read location `http://localhost:43827/v3/api-docs`"] org.kie.kogito.integrationtests.springboot.PMMLRegressionTest.testEvaluateLinRegResult1 expectation failed.Expected status code <200> but was <404>. org.kie.kogito.integrationtests.springboot.PMMLTreeTest.testEvaluateSampleMineResult1 expectation failed.Expected status code <200> but was <404>. org.kie.kogito.integrationtests.springboot.PingPongMessageTest.testPingPongBetweenProcessInstancesAssertion condition defined as a org.kie.kogito.integrationtests.springboot.PingPongMessageTest 1 expectation failed.Expected status code <200> but was <404>. within 10 seconds. org.kie.kogito.integrationtests.springboot.ProcessSvgAddonTest.testGetSvgProcessInstancesjavax/servlet/DispatcherTypeorg.kie.kogito.integrationtests.springboot.ProcessSvgAddonTest.testInvalidSvgProcessInstancesCould not initialize class com.github.tomakehurst.wiremock.jetty9.JettyHttpServerFactory |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information The version of Java (11.0.20) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17. |
(tests) - kogito-runtimes job Reproducerexport BUILD_MVN_OPTS_CURRENT=-T 1C -Dvalidate-formatting -Prun-code-coverage NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Test results:
Those are the test failures: org.kie.kogito.persistence.kafka.KafkaProcessInstancesIT.testFindByIdReadModeexpected: 5 but was: 0 |
(tests) - kogito-apps job Reproducerexport BUILD_MVN_OPTS_CURRENT= NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Test results:
Those are the test failures: Build projects / org.kie.kogito.it.jobs.ProcessAsyncIT.testAsyncjava.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details |
* Quarkus 3: update patches * [Quarkus 3] Updated rewrite data * Quarkus 3: updates patches * update patch * Updated recipe * update recipe * [Quarkus 3] Updated rewrite data --------- Co-authored-by: radtriste <[email protected]> Co-authored-by: Jenkins CI <[email protected]>
Many thanks for submitting your Pull Request ❤️!
Please make sure that your PR meets the following requirements:
KOGITO-XYZ Subject
[0.9.x] KOGITO-XYZ Subject
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
for pull request checks
Please add comment: Jenkins retest this
for a specific pull request check
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests
for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch
for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch
for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main
for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-main
for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts
for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts
for native checks
Run native checks
Please add comment: Jenkins run native
for a specific native check
Run native checks
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native
for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts
for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native-lts
Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.
Quarkus-3 PR check is failing ... what to do ?
The Quarkus 3 check is applying patches from the `.ci/environments/quarkus-3/patches`.The first patch, called
0001_before_sh.patch
, is generated from Openrewrite.ci/environments/quarkus-3/quarkus3.yml
recipe. The patch is created to speed up the check. But it may be that some changes in the PR broke this patch.No panic, there is an easy way to regenerate it. You just need to comment on the PR:
and it should, after some minutes (~20/30min) apply a commit on the PR with the patch regenerated.
Other patches were generated manually. If any of it fails, you will need to manually update it... and push your changes.