Fixed
Status Update
No update yet.
Comments
sp...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
sp...@google.com
Almost 2 months later and this is still broken
bl...@google.com
bl...@google.com
an...@google.com
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
Description
Currently, if a user runs
gradlew updateLintBaselineand there is aLintErrorissue (i.e.,"Unexpected failure during lint analysis (this is a bug in lint or one of the libraries it depends on)..."), theLintErrorissue gets added to the lint baseline xml.In cases like this, the build should fail, and the lint baseline should not be modified.