-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Azure ML extension throws warnings even after muting the warnings by only_show_errors #7560
Comments
Thank you for opening this issue, we will look into it. |
Thanks for bringing this to our attention. Those class messages are not errors, they're log warnings. All of our experimental classes are marked with a decorator to let users know that they are experimental, so that they don't use them in prod builds, or at the very least are cautious about doing so. This handled by a call to Python's logger and Python sends all logs to stderr; however, the @yonzhan I've removed the ml labels |
@diondrapeck I think @eddmik It is not recommended to use |
@bebound thank you for your comment, I have read the comments, however it is only in the case where |
@bebound Gotcha. I just checked and knack isn't GA yet, so due to Azure SDK for Python guidelines, we can't depend on it in our GA ML SDK (which the ml CLI extension is built on top of). |
Use |
Describe the bug
In the Azure Devops Pipeline I do not want to receive any warnings as the pipeline fails. Therefore my idea was to mute the warning s by only-show-errors. Still I am recevieng the following messages that make my pipeline to file however the job is submitted. When running on compute instance it does not throw an error but the message about classes are there.
Related command
Errors
Issue script & Debug output
Expected behavior
Expected behavior is not to throw any warnings not to break the pipeline, or if it is an error to understand what error is it. When running on compute instance it does not throw an error but the message about classes are there. So please give me a solution to run
az ml
commands in Azure Devops Pipeline and not fail for nothing.Environment Summary
Additional context
No response
The text was updated successfully, but these errors were encountered: