tree 2179d13e657fa6206c64bc1a1ea44ddb0412e299
parent 35e984fc9be311182231004b2d0829ade5122d5b
author Michael Klimushyn <mklim@google.com> 1573606047 -0800
committer GitHub <noreply@github.com> 1573606047 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdy1KfCRBK7hj4Ov3rIwAAdHIIAJU4HvawSz/ppEUVJ22Zifl3
 dDFoRXgAyPytS62QS2ASQt6jpaAoDrId1sNVwWLDn/cPjLs9wAQnI5GQoTy4lAf9
 QeupsK2AIqrRvGLO1L06estfZ9b8QOCEKvRk+Hj6ZfHWQfpI1uyY+YI/stgwk30r
 +8hn/NWicYLRr7bKBim+deCZ/Qsj+X540j+c5EETNRdOSneRugeyGghvnebB9ldQ
 x5fwHbI591wYeVBS9m74ye6VpKIyEw2CjPbLCmxZQqbW3k00UuTbhNML0/FAe+Dc
 z4Z7ueSzs30m/ZEBuPaIIEfTONcgiQZmvL1XOGrBJeiytS76D2AtIHhnMoTw6q8=
 =IoQA
 -----END PGP SIGNATURE-----
 

[infra] Ignore analyzer issues in CI (#2271)

35e984fc migrated some deprecated analyzer warnings to the newer
alternatives. These created some failures in unrelated plugins based on
the warnings being slightly different.

Added `ignore`s for now to turn CI green again as soon as possible. The
previous analysis options really should not be used and the majority of
the patch was unrelated, so I prefer ignoring specific already failing cases
to reverting in this case. Including an `analysis_options.yaml` file with
deprecated analyzer rules causes analyzer failures in the including package,
so that patch can't be landed in a way that prevents regressions
without updated rules.