gitgabrio commented on PR #3604: URL: https://github.com/apache/incubator-kie-kogito-runtimes/pull/3604#issuecomment-2270474195
@elguardian @fjtirado Long story short: 1. the failures are related to the modules nested below `integration-tests-springboot-processes-persistence-it` 2. they fails also on the main branch, if executed stand alone (i.e. `mvn clean install` inside `target/it/integration-tests-springboot-processes-persistence-it/(module_name)` ) 3. after different attempts, I get to the conclusion that those tests are never invoked in main, because `integration-tests-springboot-processes-persistence-it` is misconfigured 4. adding `invoker.goals = clean install` to `integration-tests-springboot-processes-persistence-it/invoker.properties` actually makes them run, and then the failures become evident (see [reference](https://maven.apache.org/components/plugins/maven-invoker-plugin/run-mojo.html#invokerPropertiesFile)) 5. without that, the nested project are compiled but not executed, and actually there is no trace of their execution anywhere (no failsafe-report, no surefire-report) 6. I have the impression those tests have been simply copied and pasted from the quarkus ones, adapted as "mvn invoker", but I can't tell if they have ever been actually executed or simply merged without double checking (maybe something else changed over time) 7. looking at code, it is clear to me why they fails, since the http requests lack some required parameter, but what it is not clear, yet, is how they works on quarkus side, so I'm currently working on that. Any hints/hindsight/suggestion would be greatly appreciated. -- 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]
