Skip to content
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 2.16.12.Final bump #1818

Merged
merged 1 commit into from
Oct 26, 2023
Merged

quarkus 2.16.12.Final bump #1818

merged 1 commit into from
Oct 26, 2023

Conversation

porcelli
Copy link

quarks bump to 2.16.12.Final

@porcelli
Copy link
Author

@mariofusco I sense you left this behind in the quarkus upgrade PRs

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 24, 2023

PR job #1 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer

build-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-examples -u #1818 --skipParallelCheckout

NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1818/1/display/redirect

Test results:

  • PASSED: 378
  • FAILED: 1

Those are the test failures:

org.kie.kogito.quarkus.outbox.OutboxIT.(?) org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (172.17.0.1 ports: [8083, 39383] should be listening)

@porcelli
Copy link
Author

what are the thoughts about the failing test? I can't see how it relates.. looks like an env problem (Timed out).

@jstastny-cz any input?

@jstastny-cz
Copy link

OutboxIT is often unstable.

@baldimir
Copy link
Contributor

If it is unstable, I would say let's fix it or delete it. Of course in a separate PR.

@jstastny-cz
Copy link

If it is unstable, I would say let's fix it or delete it. Of course in a separate PR.

@baldimir Go ahead. That's what I asked for in the dev mailing list. I am not able to fix it myself and I don't have insight into how useful this example actually is.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 26, 2023

PR job #2 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer

build-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-examples -u #1818 --skipParallelCheckout

NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1818/2/display/redirect

Test results:

  • PASSED: 374
  • FAILED: 3

Those are the test failures:

org.kie.kogito.examples.quarkus.DashboardsListIT.testDashboardsListIsAvailable java.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details
org.kie.kogito.quarkus.outbox.OutboxIT.(?) org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (172.17.0.1 ports: [8083, 42037] should be listening)
org.kie.kogito.springboot.outbox.OutboxIT.(?) org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (172.17.0.1 ports: [8080, 42084] should be listening)

@porcelli
Copy link
Author

failing tests are unrelated and has been identified as flaky before as mentioned by @jstastny-cz - I'll move forward and merge

@porcelli porcelli merged commit f0bb5db into apache:main Oct 26, 2023
1 check failed
rgdoliveira pushed a commit to kiegroup/kogito-examples that referenced this pull request Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants