Pull request overview

• Fix Move ShowRunnerOutput's show_output function to C++ so both Ruby and Python can use it #5452
• Deprecate ShowRunnerOutput's show_output and implement C++ WorkflowStepResult::showOutput() so both Ruby and Python can use it

I have tested that there are no changes in output (actually: just a tiny bit) in 3.10.0 versus this branch.

3.10.0 versus this branch, still using "require 'openstudio/measure/ShowRunnerOutput.rb' and calling show_output: only diff is the placement of the second "undefined stepResult"

--- ../../RubyModelMeasure/tests/ori.log	2025-07-10 13:00:04.357705477 +0200
+++ ../../RubyModelMeasure/tests/new_back.log	2025-07-10 13:00:04.378705844 +0200
@@ -1,8 +1,9 @@
+[ShowRunnerOutput.rb] <0> Deprecated at 3.11.0, use WorkflowStepResult::showOutput() instead
 [openstudio.measure.OSRunner] <1> Cannot find current Workflow Step
 [openstudio.WorkflowStepResult] <0> WorkflowStepResult value called with undefined stepResult, returning 'Success'
-[openstudio.WorkflowStepResult] <0> WorkflowStepResult value called with undefined stepResult, returning 'Success'
 
 **MEASURE APPLICABILITY**
+[openstudio.WorkflowStepResult] <0> WorkflowStepResult value called with undefined stepResult, returning 'Success'
 0 = Success
 **INITIAL CONDITION**
 The building started with 4 spaces

Running with result.showOutput() instead, the only difference is that the Deprecation warning is gone. And Python and Ruby both produce exactly the same output.

[openstudio.measure.OSRunner] <1> Cannot find current Workflow Step
[openstudio.WorkflowStepResult] <0> WorkflowStepResult value called with undefined stepResult, returning 'Success'

**MEASURE APPLICABILITY**
[openstudio.WorkflowStepResult] <0> WorkflowStepResult value called with undefined stepResult, returning 'Success'
0 = Success
**INITIAL CONDITION**
The building started with 4 spaces.
**FINAL CONDITION**
The building finished with 5 spaces.
**INFO MESSAGES**
Space New Space was added.
**WARNING MESSAGES**
**ERROR MESSAGES**
***Machine-Readable Attributes**
[
{
   "name" : "space_name",
   "value" : "New Space"
},{
   "display_name" : "New Space Name",
   "name" : "new_space_name",
   "value" : "New Space"
}
]
***Files Generated**

I don't really like the ***Machine-Readable Attributes** formatting.

Pull Request Author

• Model API Changes / Additions
• Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
• Model API methods are tested (in src/model/test)
• EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
• If a new object or method, added a test in NREL/OpenStudio-resources: Add Link
• If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
• Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
• All new and existing tests passes
• If methods have been deprecated, update rest of code to use the new methods

Labels:

• If change to an IDD file, add the label IDDChange
• If breaking existing API, add the label APIChange
• If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

Review Checklist

This will not be exhaustively relevant to every PR.

• Perform a Code Review on GitHub
• Code Style, strip trailing whitespace, etc.
• All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
• Labeling is ok
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified