-
Notifications
You must be signed in to change notification settings - Fork 120
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
VerifyMojo doesn't log warnings, but simply ignores them #2714
Comments
@maxonfjvipon please, help |
@levBagryansky can you take it? |
@maxonfjvipon sure |
levBagryansky
added a commit
to levBagryansky/eo
that referenced
this issue
Feb 7, 2024
levBagryansky
added a commit
to levBagryansky/eo
that referenced
this issue
Feb 7, 2024
levBagryansky
added a commit
to levBagryansky/eo
that referenced
this issue
Feb 7, 2024
levBagryansky
added a commit
to levBagryansky/eo
that referenced
this issue
Feb 7, 2024
Merged
levBagryansky
added a commit
to levBagryansky/eo
that referenced
this issue
Feb 7, 2024
levBagryansky
added a commit
to levBagryansky/eo
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now,
VerifyMojo
, iffailOnWarning
isfalse
does nothing with the warnings. However, it should log them throughLogger.warn
. I think, it should log everything (errors, critical, warnings), and only then either fail the build or not.The text was updated successfully, but these errors were encountered: