-
Notifications
You must be signed in to change notification settings - Fork 222
Comment out debug print statements #5200
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
Conversation
| "-m,--measures_only", | ||
| [opt](std::int64_t val) { | ||
| fmt::print("val={}\n", val); | ||
| // fmt::print("val={}\n", val); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally ok here
| int ex = ruby_cleanup(0); | ||
| if (ex != 0) { | ||
| fmt::print("RubyEngine return code was {}\n", ex); | ||
| // fmt::print("RubyEngine return code was {}\n", ex); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I want this one gone...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't seem like standard practice to print the exit code? After all, anyone can easily obtain the exit code themself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The message was to explain why it returned a non zero exit code.
When running something like
OpenStudio/src/cli/test/at_exit.rb
Lines 1 to 3 in 20d91f5
| at_exit { | |
| exit 12 | |
| } |
But sure, I suppose that's fine removing it
c7d1a59 to
eeb4e67
Compare
|
CI Results for eeb4e67:
|
|
Don't know what CI is tripping on, but this is fine. |
Pull request overview
Comment out debug print statements