-
Notifications
You must be signed in to change notification settings - Fork 215
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
logging.info not showing up in console output #46
Comments
Console output default level is warning. if you want to see the info level logging, use flag "--verbosity info". --verbosity is for console level logging, for log file level, use "--log_file" to set the log file name, use "--log_level" to set the log file logging level. (debug, info, warning, error, critical). |
I added --verbosity info and I see the INFO about starting the phase |
We separated framework versus tester logging by design, and the command line flags were set up to control framework logging, with tester logging going to the test record (and from there to the output module). Maybe we can talk about this at our next in person meeting and see how we should handle the need for tester console output. |
I've been adding the following to my phases and I'm able to see the output. Maybe openhtf can do something similar? import logging |
Ran from head, I see output in the expected places, closing issue |
Not seeing logging.info() show up in the console output.
In the example I don't see the "Tearing Down" or if I add logging.info to the phase I don't see output.
The text was updated successfully, but these errors were encountered: