nikhiln64 commented on PR #6809: URL: https://github.com/apache/incubator-kie-drools/pull/6809#issuecomment-5029130816
@mariofusco I went deeper on this after the rerun on the rebased branch showed the same failures. The CI logs point somewhere unexpected. Right before the KJarLoadingTest errors there is a stream of warnings from MavenRepository.resolveArtifact saying it is unable to resolve org.drools.testcoverage:drools-kie-ci-with-domain-test-kjar:999-SNAPSHOT. So the tests are failing while resolving the fixture kjar through the embedded maven machinery, which happens before any class loading that this change could influence. The "Cannot find KieModule" message is what surfaces after the scanner swallows that resolution failure. I also redid the local comparison more carefully this time. I installed the test kjar and domain modules into my local repo first, then ran the kieci suite with my change applied and again with the parent commit's wiring sources reinstalled. The outcome was identical in both states every time. Given that main is green and the recently passing PRs only touched dependency versions, my best guess is that the PR build computes its module set from the diff, and when only drools-wiring changes the test kjar does not get built into the repository the kieci tests resolve from. Is that a known quirk of the kieci standalone suite? If there is a preferred way to debug or force the kjar build in the PR pipeline I am happy to do it, and equally happy to be proven wrong if you see a real interaction here. -- 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]
