Fixed
Status Update
Comments
tn...@google.com <tn...@google.com>
tn...@google.com <tn...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Are you reporting this as a Developer or User?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Are you reporting this as a Developer or User?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
sh...@pinterest.com <sh...@pinterest.com> #3
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
tn...@google.com <tn...@google.com> #4
We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.
sh...@pinterest.com <sh...@pinterest.com> #5
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 aLintWarning
instead? 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