New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
verifyPaparazzi
false positives when running testDebug
with Gradle caching enabled, becomes unreliable with Gradle Configuration Cache
#388
Comments
Possibly related to gradle/gradle#19710? I'm curious as to whether downgrading to 7.3.3 or 7.4.1 fixes the underlying issue. |
Are you using Paparazzi 0.9.3 or latest SNAPSHOT? |
Thanks for reply 🙏 I'll describe the scenarios I'm testing right now:
In scenario I definitely observe behaviour change between Gradle 7.3.3 and 7.4.
I'm using the latest Snapshot. Which at this very moment is whatever being published from the main branch. |
Just tried on |
Very likely fixed by #690 |
Fixed by #690 |
Repro:
org.gradle.caching=true
enabled./gradlew testDebug
- task succeeds./gradlew verifyPaparazziDebug
- tasks succeeds despite it should fail because the UI has been modifiedlooking at the details, when invoking step 4)
testDebug
does not run with because their inputs hasn't been modifiedwhich then ignores properties set by Paparazzi Gradle Plugin
this also may lead to even more unexpected behaviour if one have
--configuration-cache
enabled - it seems like the system properties are cached, which means invokingrecordPaparazziDebug
before any other task will always passpaparazzi.test.record=true
to test task, which in my case led toverifyPaparazzi
recording new screenshots.The text was updated successfully, but these errors were encountered: