-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Treat unit tests warnings as errors #312
Conversation
/cc @rbradford I think this is fixing #309 :) |
Although this is definitely an improvement - catching errors in the test build. I don't think it is the equivalent of |
Well I know this is different but this is eventually reaching the same goal of "not allowing warnings to be missed". |
Now that CpuInfo::parse_from() returns a Result, a warning was showing up saying the result should be handled. Signed-off-by: Sebastien Boeuf <[email protected]>
Turn on the rustc flag "-Dwarnings" for all bazel rust tests so that all warnings would show up as errors. Signed-off-by: Sebastien Boeuf <[email protected]>
This is definitely an improvement but it doesn't solve #309 which is about clippy not covering the tests as clippy warns about things that rustc doesn't. |
Thanks, I merged this, then reopened 309. |
Turn on the rustc flag
-Dwarnings
for all bazel rust tests so that all warnings would show up as errors.Fixes #309