Skip to content
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

Unable to use --warnings-as-errors to fail CI on compilation warnings #16

Open
axelson opened this issue Jan 19, 2022 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@axelson
Copy link
Contributor

axelson commented Jan 19, 2022

I'm having trouble getting mix_machine to work how I'd expect it to. I want to use mix_machine in CI and have it cause CI to fail if there's a compilation warning. But if I use mix compile.machine --warnings-as-errors and there's a compilation warning then the sarif report doesn't get generated. And if I don't use --warnings-as-errors then CI doesn't fail. However when not in the CI environment (GitHub actions) mix compile.machine --warnings-as-errors does generate a report.

I'm testing with:

It looks like the Mix.Task.run("compile", argv) never returns

@hauleth hauleth self-assigned this Jan 19, 2022
@hauleth hauleth added the bug Something isn't working label Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants