Conversation
memory leak fixed for first two pvwattsv8 tests but remains if all pvwattsv8 tests are run
rewrite create_weatherdata_array and free_weatherdata_array
rewrite create_winddata_array and free_winddata_array
…on, fix memory leak in sscapi_test, json_to_ssc_data
…n_to_ssc_data calls with ssc_data_free
…etest causes memory leaks on windows when failures reported
… leaks on Windows 10 CMPvsamv1BatteryIntegration_cmod_pvsamv1.LCOS_test_cashloan"; // pass with many memory leaks windows 10 CMPvsamv1BatteryIntegration_cmod_pvsamv1.ResidentialDCBatteryModelPriceSignalDispatch"; // pass with many memory leaks windows 10
…ng memory leaks in tests
|
No memory leaks on macOs 12.0.1 and all tests passing on Github Actions and Windows. Questions and comments and updated practices are welcomed! |
|
The jc-community contributor seems to occur from a different computer I was testing and updating on... interesting how they came into existence... |
|
There are 6 failing tests only on macOS 12.0.1 with the Apple Silicon chip with maybe too tight of tolerance: [ RUN ] voltage_table_lib_battery_voltage_test.calculateMaxChargeHourly1 |
|
Ignore my previous comment - I was running the tests on patch and failed to check out this branch. |
|
No SEH exceptions in one run on Windows (much better than usual!) The test results make it look like increasing the tolerance is a reasonable option. It looks like most could be increased by 10%, while those currently set to a value of "1" should perhaps be "2". |
Matthew-Boyd
left a comment
There was a problem hiding this comment.
The fixed memory leaks and other changes in the CSP files look great, thank you very much for doing this! I guess we'll have to make good lasting impressions now.
Note that lib_battery_voltage_test.cpp line 709 had to be increased from 1e-3 to 2e-2 to pass.
Updated in commit 63b343e with noted tolerance update in detailed commit message. I would like to merge sooner than later so I do not need to keep updating tests that are modified on the patch branch without these changes ;-) |
cpaulgilman
left a comment
There was a problem hiding this comment.
FYI -- these changes to not seem to affect simulation run times, test results generated in Windows 10, Intel Core i5-6400 2.7GHz CPU 4 Cores, 32 GB RAM, no SSD hard drive:
@cpaulgilman, the column titles in the spreadsheet have 'release' and 'patch'... is the 'release' the patch branch of ssc and the 'patch' branch the ssc_719 branch of ssc (this branch)? I am not sure why ETES Single Owner is now taking 63s longer.... |
Thank you and thank you for the quick review! |
Yes, patch = ssc_719 and release = SAM 2021.12.02. |
No description provided.