Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5472

Debug enabled scenarios are failing in kogito builder image

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 1.9.0.Final
    • None
    • Image
    • None
    • False
    • False
    • Undefined
    • Hide
      • git clone https://github.com/kiegroup/kogito-examples.git
      • git checkout nightly-master
      • mvn clean package -DskipTests -U
      • s2i build target/ quay.io/kiegroup/kogito-runtime-jvm-nightly:temp-master-tests process-springboot-example:1.0
      • docker run -e JAVA_OPTIONS=-Ddebug=true -e RUNTIME_TYPE=springboot process-springboot-example:1.0
      Show
      git clone https://github.com/kiegroup/kogito-examples.git git checkout nightly-master mvn clean package -DskipTests -U s2i build target/ quay.io/kiegroup/kogito-runtime-jvm-nightly:temp-master-tests process-springboot-example:1.0 docker run -e JAVA_OPTIONS=-Ddebug=true -e RUNTIME_TYPE=springboot process-springboot-example:1.0

      There has been some changes in Kogito runtimes and now the Kogito builder tests where debug is enabled (3 scenarios) are failing due to:

      And container log should contain main] .c.l.ClasspathLoggingApplicationListener
      

      Failing scenarios:

      • Verify if the s2i build is finished as expected with debug enabled
      • Verify if the s2i build is finished as expected with no runtime image and debug enabled
      • Verify if the s2i build is finished as expected using multi-module build with debug enabled

      This is blocking the Kogito builder nightly update and so bdd testing using that one.

       

              vajain Vaibhav Jain
              tradisso@redhat.com Tristan Radisson
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: