Any ideas are welcome, I see in CI log ```BUILD SU...
# community-support
e
Any ideas are welcome, I see in CI log
Copy code
BUILD SUCCESSFUL in 4m 52s
8275 actionable tasks: 2679 executed, 227 from cache, 5369 up-to-date
I'm assuming gradle is finished and succeed but just after I see next
Copy code
FAILURE: Build failed with an exception.

* What went wrong:
Java heap space

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at <https://help.gradle.org>.

BUILD FAILED in 4m 53s
So gradle failed. I wonder, why gradle prints build final status two times?
🤯 1
We are on the latest gradle (8.9)
v
Hard to say without the stacktrace. But I guess what happens is, that after the build is finished, some more things happen like cache cleanup and so on. And during that the OOME happens and causes another build finished status to be printed with failed.
e
Thanks, let me add --stacktrace and try to catch it