New boost (>= ~1.74) based unit tests started using sysconf() to determine signal stack size which at this moment is not supported by OSv implementation. These results in errors looking like this:
"Test setup error: std::bad_alloc: std::bad_alloc" which are happily ignored by our error pattern detection logic in testing.py. This patch adds one more failure pattern. Signed-off-by: Waldemar Kozaczuk <[email protected]> --- scripts/tests/testing.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/tests/testing.py b/scripts/tests/testing.py index a1cdec35..50b49c08 100644 --- a/scripts/tests/testing.py +++ b/scripts/tests/testing.py @@ -81,7 +81,8 @@ def scan_errors(s,scan_for_failed_to_load_object_error=True): "at org.junit.runner.JUnitCore.main", "ContextFailedException", "AppThreadTerminatedWithUncaughtException", - "\[backtrace\]" + "\[backtrace\]", + "Test setup error" ] if scan_for_failed_to_load_object_error: -- 2.35.1 -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/20220511214915.143995-1-jwkozaczuk%40gmail.com.
