Closed kbenne closed 4 months ago
@kbenne can you do a quick walkthrough with some comments please?
I rebased onto develop after marking it "Ready for CI" so that CI tries to build it. Curious to see if the windows logger test is fixed
Windows failing logger test in "classic" CLI
1/1 Test #3731: OpenStudioCLI.Classic.test_logger_rb ...***Failed 0.87 sec
Namespace(classic=True, logger_file=WindowsPath('D:/git/OpenStudio/src/cli/test/logger_test.rb'), os_cli_path=WindowsPath('D:/git/OpenStudio/build/Products/openstudio.exe'))
Running: D:\git\OpenStudio\build\Products\openstudio.exe classic execute_ruby_script D:\git\OpenStudio\src\cli\test\logger_test.rb
0 LOGGER - STDOUT Warn
1 LOGGER - STDOUT Error
Traceback (most recent call last):
File "D:/git/OpenStudio/src/cli/test/run_test_logger.py", line 50, in <module>
raise IOError(f"Expected 3 lines, got {n}")
OSError: Expected 3 lines, got 2
So that OpenStudio::logFree(OpenStudio::Error, "test", "Error")
is not printed to the stdout
CI Results for c162c0492a6ba4ec061bfccd159d85286aedb450:
Ubuntu 20.04:
Ubuntu 22.04:
Darwin:
Windows:
Code Coverage:
Supperseded by #5119
@jmarrec I think this should address the core issue that the logger is not global across the script engines. I think there remains a little bit of work.
SHARED_OS_LIBS
. What do you think?if Windows
conditions that attempted to work around the issue.