Hello Divesh,

I have a similar error, with the PR 987 [1], CodeQL failed with just 'parsing failed' on task compilGroovy after a rebase on trunk

I reproduce in local, but failed to debug it at this time

Nicolas

[1] https://github.com/apache/ofbiz-framework/pull/987
On 5/29/26 15:42, Divesh Dutta wrote:
Hi all,

I also analysed debug-artifacts-java produced during runtime from here:

https://github.com/apache/ofbiz-framework/actions/runs/26632756209

I  did not find any evidence pointing to the Groovy file that I added in
the PR. The logs show the failure happens during CodeQL autobuild / Gradle
testClasses, but they do not surface a specific error in
ProductionRunQueryServices.groovy .

Thanks
--
Divesh Dutta
www.hotwaxsystems.com

On Fri, May 29, 2026 at 6:00 PM Divesh Dutta<[email protected]>
wrote:

Hi all,

I’m seeing a CodeQL Java analysis failure in GitHub Actions on PR #1299 :

https://github.com/apache/ofbiz-framework/pull/1299


The job fails during the CodeQL autobuild step while running:

./gradlew --no-daemon ... testClasses

What I can see from the logs:


    - compileJava complete
    - compileGroovy starts
    - the build then fails with a generic parsing failed
    - the log also shows many classpath warnings such as bad path element
    and Unexpected file on path


I’m currently unable to reproduce the failure locally on Java 17:


    - ./gradlew compileGroovy passes
    - ./gradlew codenarcMain passes
    - ./gradlew check javadoc passes


The relevant PR adds a production-run read/query service file:


    -
    
applications/manufacturing/src/main/groovy/org/apache/ofbiz/manufacturing/jobshopmgt/ProductionRunQueryServices.groovy
    - service defs in
    applications/manufacturing/servicedef/services_production_run.xml


At the moment I don’t have a concrete Groovy file/line from the CodeQL
run, so I’m trying to determine whether this is:


    - a CodeQL autobuild/environment issue,
    - a build/classpath issue in CI,
    - or a repo-wide Groovy compilation problem that isn’t reproducing
    locally.


If anyone has seen a similar compileGroovy failure under CodeQL autobuild
with Java 17 / Gradle 8.14.5, I’d appreciate pointers on where to look next.

Thanks
--

Divesh Dutta
www.hotwaxsystems.com

Reply via email to