ricardozanini commented on PR #2892:
URL: 
https://github.com/apache/incubator-kie-tools/pull/2892#issuecomment-2638191964

   Regarding jobs-service:
   
   ```
       Scenario: verify if container starts as expected                         
                                                                    # 
features/image/kogito-jobs-service-postgresql.feature:35
         When container is started with env                                     
                                                                    # 
steps/container_steps.py:72
           | variable                    | value                                
                 |
           | SCRIPT_DEBUG                | false                                
                 |
           | QUARKUS_LOG_LEVEL           | DEBUG                                
                 |
           | QUARKUS_DATASOURCE_DB_KIND  | postgresql                           
                 |
           | QUARKUS_DATASOURCE_USERNAME | test                                 
                 |
           | QUARKUS_DATASOURCE_PASSWORD | 123456                               
                 |
           | QUARKUS_DATASOURCE_JDBC_URL | 
jdbc:postgresql://10.11.12.13:5432/hibernate_orm_test |
         Then container log should contain -Dquarkus.http.host=0.0.0.0 
-Dquarkus.http.port=8080 -jar "/home/kogito/bin/quarkus-app/quarkus-run.jar" # 
steps/container_steps.py:31
     2025-02-05 20:46:36,711 container_steps.py:215        INFO  Message 
'-Dquarkus.http.host=0.0.0.0 -Dquarkus.http.port=8080 -jar 
"/home/kogito/bin/quarkus-app/quarkus-run.jar"' was found in the logs
         And container log should contain  Trying to establish a protocol 
version 3 connection to 10.11.12.13:5432                                  # 
steps/container_steps.py:31
           Traceback (most recent call last):
             File 
"/home/runner/work/incubator-kie-tools/incubator-kie-tools/packages/python-venv/venv/lib/python3.12/site-packages/behave/model.py",
 line 1329, in run
               match.run(runner.context)
             File 
"/home/runner/work/incubator-kie-tools/incubator-kie-tools/packages/python-venv/venv/lib/python3.12/site-packages/behave/matchers.py",
 line 98, in run
               self.func(context, *args, **kwargs)
             File "steps/container_steps.py", line 34, in log_contains_msg
               raise Exception("Message '%s' was not found in the logs" % 
message)
           Exception: Message ' Trying to establish a protocol version 3 
connection to 10.11.12.13:5432' was not found in the logs
   ```
   
   I verify it by spinning up the container and checking for the logs to see if 
the message exists. I can't check this today.
   
   For the `sonataflow-builder`, the same thing in this test:
   
   ```
    Scenario: Verify that the application is built and started correctly        
                                                        # 
features/image/sonataflow-builder.feature:4
         When container is started with command bash -c 
'/home/kogito/launch/build-app.sh && java -jar 
target/quarkus-app/quarkus-run.jar' # steps/container_steps.py:106
           | variable     | value |
           | SCRIPT_DEBUG | false |
         Then check that page is served                                         
                                                           # steps/steps.py:122
           | property             | value           |
           | port                 | 8080            |
           | path                 | /q/health/ready |
           | wait                 | 480             |
           | request_method       | GET             |
           | expected_status_code | 200             |
     2025-02-05 20:47:45,190 steps.py:165        INFO  Checking if the 
container is returning status code 200 on port 8080
     ```
     
     Perhaps some incompatibility with Quarkus 3.15.x. 
     
     I can take a look tomorrow only.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to