Skip to content
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

Tests not retreived from cache when project is relocated #1570

Open
ribafish opened this issue Sep 4, 2024 · 0 comments
Open

Tests not retreived from cache when project is relocated #1570

ribafish opened this issue Sep 4, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ribafish
Copy link
Contributor

ribafish commented Sep 4, 2024

Paparazzi is supplying a bunch of absolute paths to all of test tasks system properties here and here, which means that relocatability is broken when using the paparazzi plugin... This is causing cache misses when project is relocated and the absolute paths change, which also renders remote cache unusable for this purpose, as different machines usually have different absolute paths. This issue affects all test tasks in projects where paparazzi plugin is applied, regardless of whether they actually have paparazzi tests.

Steps to Reproduce

  1. Run a build with paparazzi plugin applied
  2. Move/copy the project to a different location
  3. Run a second build with paparazzi plugin applied
  4. Observe the test tasks were executed with no code changes, in which case you'd expect to get them from cache.

Expected behavior
Applying the paparazzi plugin doesn't break caching of test tasks.

Additional information:

  • Paparazzi Version: 1.3.4
  • OS: MacOs
  • Compile SDK: 34
  • Gradle Version: 8.10
  • Android Gradle Plugin Version: 8.4.2
@ribafish ribafish added the bug Something isn't working label Sep 4, 2024
@ribafish ribafish changed the title Test results not retreived from cache if Tests not retreived from cache when project is relocated Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant