This message was deleted.
# community-support
s
This message was deleted.
s
I do have caching enabled in gradlle.properties
Copy code
org.gradle.caching=true
I am able run `` ./gradlew clean build jacocoTestReport`` locally without any issues. It fails when it runs the same in a build pipeline
v
Maybe you get more info with
--stacktrace
if the actual error was not logged.
s
Thank you, I was able to resolve it. It had something to do with my test-container setup.
👌 1
@Vampire I have a constatnt issue with iTests. When I run a single file with iTests, the tests pass. If I run all the iTests in my project then tests start failing.
The tests are soo flaky and I am having really hard time with it.
v
Well, fix it. :-D
o
Fixing flaky tests is definitely something I would recommend, and happy to share some materials @Swathi Balasubramanya Ayas At the same, better error propagation should happen for the default configuration. @Swathi Balasubramanya Ayas could you please share a little bit more about the root cause of the issue and which Gradle/Plugin versions you use? I will for an issue to the JaCoCo plugin
v
You think the issue with flaky tests she has after fixing the JaCoCo issue is caused by the JaCoCo plugin? How so? Because of the agent that is added?
o
I don't think so, there is no evidence to suggest that the plugin is responsible somehow. What I mean is better diagnostic message. That would help to troubleshoot it quickly. It is RFE not a bug
v
You mean for the JaCoCo failure that just said "Error while creating report" I guess, not the actual problem of flaky tests?
o
Yes. At least some error propagation would be nice, without the need to increase the log level
👌 1