In our CI environment, we run our tests with this command: mix test --warnings-as-errors <files>
This is intended to fail when someone has created a warning within a test file in addition to when the tests themselves fail. We have an earlier check (MIX_ENV=test mix compile --force --warnings-as-errors) that validates that our production code is warning-free, but this does not compile nor validate test files. A few of our tests are somewhat finnicky, and will fail sporadically (e.g. due to PostgreSQL deadlocks). So we also have retry logic in our CI environment that will re-run tests when the above command exists unsuccessfully (exit code != 0). However, no amount of re-running will fix a compilation warning! Presently, both test failures *and* compilation failures return exit code 1, and so we are not able to differentiate between the two and only re-run in the former case. Would it be appropriate to change the compilation failure case to return an exit code of, say, 2? -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/bfe6d609-c343-4760-b2c4-c8faf0bc0b99n%40googlegroups.com.
