Fixed
Status Update
No update yet.
Comments
tn...@google.com
sh...@pinterest.com
@Tor - is there any workaround for this issue other than ignoring LintError which seems fraught with danger? Is there a way to tell lint to not use this cache?
tn...@google.com
What does the error message look right? The general purpose way to suppress any issue is with a lint.xml file (which lint picks up automatically from surrounding directories but you can also point it to specific ones with command line flags or Gradle DSL.)
Here's some more documentation and a sample file --https://googlesamples.github.io/android-custom-lint-rules/user-guide.md.html#configuringusinglint.xmlfiles
Here's some more documentation and a sample file --
sh...@pinterest.com
It's:
Error: Failed to deserialize cached resource repository.
This is an internal lint error which typically means that lint is being passed a
serialized file that was created with an older version of lint or with a different
set of path variable names. Attempting to gracefully recover.
The serialized content was:
...
[LintError]
1 errors, 0 warnings
Does it seem appropriate to just suppress LintError? It doesn't seem limited to particular modules so we'd probably need to do it globally.
Description
DESCRIBE THE ISSUE IN DETAIL:
We are seeing occasional errors on CI in
LintResourceRepository.getOrCreateRepository. Based on the code and comments, this is a recoverable error, yet it still fails the lint task with aLintError(and hence fails our builds.) Should it not be aLintWarninginstead? If it's recoverable I'd expect the lint task to be able to continue.I'm also happy to file a separate bug about the errors but we don't have any repro steps, as it happens intermittently, and only on CI.
Version of Gradle Plugin: 7.2.2 Version of Gradle: 7.3.3 Version of Java: openjdk 11.0.12 2021-07-20 OS: MacOS 12.6.1