You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating Paparazzi from v1.3.1 to v1.3.4 to address OutOfMemory (OOM) errors, a significant number of tests started failing, while using maxPercentDifference: Double = 0.1. Running the ./gradlew recordPaparazziDebug command regenerated all snapshots, despite no changes in the codebase.
Steps to Reproduce
Update Paparazzi to v1.3.4.
Run ./gradlew verifyPaparazziDebug.
Observe that many tests fail unexpectedly.
Run ./gradlew recordPaparazziDebug.
Notice that all snapshots are regenerated, even though no code changes were made.
Expected Behavior
The tests should pass without regenerating snapshots unnecessarily. If there are no changes in the code, Paparazzi should load - snapshots from the cache instead of regenerating them.
Version 1.3.4 had some known changes in rendering which unfortunately would require some snapshot regen. @jrodbx was able to diagnose this change and fix it . Once our next version is out, it should fix this issue. If you want to try the latest and greatest, try using the 1.3.5-SNAPSHOT version.
You do have to re-record snapshots if there are significant changes to layoutlib. Same as how previews sometimes look a bit different / better after upgrading Android Studio.
Description
After updating Paparazzi from
v1.3.1
tov1.3.4
to addressOutOfMemory (OOM)
errors, a significant number of tests started failing, while usingmaxPercentDifference: Double = 0.1
. Running the./gradlew recordPaparazziDebug
command regenerated all snapshots, despite no changes in the codebase.Steps to Reproduce
Expected Behavior
Additional Information
Paparazzi Version: 1.3.4
OS: macOS
Compile SDK: 34
Gradle Version: 8.9
Android Gradle Plugin Version: 8.5.1
The text was updated successfully, but these errors were encountered: