|
|
|
|
|
by account42
1795 days ago
|
|
> That's even worse, because then an upgrade to the compiler in the managed CI runner (e.g. Github Actions') base-image will translate to the same version of the code failing where it previously succeeded If you don't want your build to fail on warnings, don't use -Werror. If you want it to only fail on specific warnings, use -Werror=... > with nobody sure why Unless they look at the errors in the compiler output. What does it matter if it was brought on by a compiler update or a push? > At least with -Werror on at all times, devs will tend to upgrade before the very-stable CI environment does Nothing wrong with -Werror for devs - the problem is when you ship code to others and leave -Werror on by default. |
|