-
Notifications
You must be signed in to change notification settings - Fork 13
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
Build-time failures hang heavy-test build jobs #135
Comments
It seems the thread is just waiting for something:
|
No idea... 😅 |
Let see if PR #151 works. |
#154 should fix it. |
We'll see as soon as the old-libs test is done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checking the following test reports:
https://libraries.openmodelica.org/branches/heavy_tests/ScalableTestSuite_NB/ScalableTestSuite_NB.html
https://libraries.openmodelica.org/branches/heavy_tests/ScalableTestSuite_OB/ScalableTestSuite_OB.html
https://libraries.openmodelica.org/branches/heavy_tests/LargeTestSuite_NB/LargeTestSuite_NB.html
https://libraries.openmodelica.org/branches/newInst-newBackend/ScalableTestGrids_noopt/ScalableTestGrids_noopt.html
it is apparent that timeouts during C-compile time and run time are reported correctly and take place after the specified BuildModel time limit and Simulation time limit. For some reason, timeouts during code generation seem not to be reported correctly to the Python script, which then duly waits two times the BuildModel timeout + the Simulation time limit + 25 extra seconds before failing, without any report at all.
This makes the testing time much longer, because of the unnecessary very long waiting times, and prevents displaying proper diagnostic logs.
@adrpo can you please figure out what's wrong here and correct it?
Thanks!
The text was updated successfully, but these errors were encountered: