tree 1197b139854d68db87543447977b3b7514092476
parent bc0578798f50d018ca4278ad5610598c400992c9
author Damien Elmes <dae@users.noreply.github.com> 1607385977 +1000
committer GitHub <noreply@github.com> 1607385977 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfzsN5CRBK7hj4Ov3rIwAAdHIIAGH0N2v1KNKKrJt3IT/D/mVV
 fayy/nZLuBymXTYuNAaownCspNW+0nZmX1Nask/+t4cmvRh6bzGj3/m/0BZIw+FM
 h0VKIPdGYdivFFFBhawlaBPMxvECXtUScAQqaUtPAxo3M5OX27cuGho+K8ws69+p
 /7ZDF4/EjMq6NUiSmnwMaMmWbF04XR5hPLlmkgMIcLug2Y0a1wM+fYmIqkWOZ/yu
 uCIRsIhJyLGPmIT+ihYeC9LwaIO5DBfRuVNtHyvblQuya4+AV7DCEUgKzetlknPL
 Dl1rMcgGl/Big3b6X5wUA1u//dMctb9YDopp/TbZgIpKrdHrgvPI59sCLdCkkKM=
 =3Gog
 -----END PGP SIGNATURE-----
 

fail build on any warnings when running clippy (#456)

* fail build on any warnings when running clippy

Currently warnings from rustc such as an unused import are printed
during first execution, but they do not fail the build. If cargo users
run clippy again, the same warnings get printed, but with Bazel nothing
is shown, as the previous success is cached.

This patch changes all warnings into errors, with the rationale being
that if we're failing for any clippy warning, it probably makes sense
to fail for rustc warnings as well.

* clippy aspect needs to include --test on command line for tests

Without it, items imported in integration tests generate unused import
warnings, which fail the build.

* tag bindgen libaries, and don't fail when they generate warnings