https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# community-support
s
This message was deleted.
m
try to run with 
--scan
, it will tell you why the tests were executed. By default Gradle will not rerun the tests if nothing changed (unless the previous test execution failed)
d
Sure TY! doing that now.
I do not see any failing tests
Do you think these count as errors for it to trigger tests again
the TEST is not failing per say but this error is logged
m
don't look at the test results, look at the test task and it will tell you why it was executed
d
sure thank you. Taking a look
It gives below info, but when I went to that path and checked the folders and file are present.
m
did you run 
clean test
or 
test
?
d
I just did build and my build.gradle has this
m
I suspect you have a plugin which breaks this. The warning about overlapping outputs is curious. So my educated guess would be that you have a plugin which deletes the test results and does something to the test tasks.
d
these are only ones i got
but thank you for all your inputs, i’ll investigate further in this direction
@melix I keep getting build-info.properties has changed and hence test task is not up to date
l
If you generate that file with a unique build identifier, then it makes the task always out of date. Have a look at docs as there are different strategies to fix that. https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:up_to_date_checks
🙏 1
d
Thank you all for your help. I am able to achieve what i wanted
Open in Slack
PreviousNext
Powered by