ichthyo/LUMIERA.clone
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
LUMIERA.clone/tests/10exception.tests

23 lines
1.5 KiB
Text
Raw Normal View History

link tests with stringent application scope dependencies (closes #938) - the tests covering threadind support and object monitors are located in the backend test-library and linked against liblumierabackend.so - some fundamental facilities of proc-layer moved from the library tree into the basic components tree, since *testing* them requires at least to link against liblumieracommon.so
2014-10-17 21:15:59 +02:00
TESTING "Exception handling and diagnostics" ./test-suite --group=common
Library: discontinue setting error flag from Exceptions (see #1341) While seemingly subtle, this is a ''deep change.'' Up to now, the project attempted to maintain two mutually disjoint systems of error reporting: C-style error flags and C++ exceptions. Most notably, an attempt was made to keep both error states synced. During the recent integration efforts, this increasingly turned out as an obstacle and source for insidious problems (like deadlocks). As a resolve, hereby the relation of both systems is **clarified**: * C-style error flags shall only be set and used by C code henceforth * C++ exceptions can (optionally) be thrown by retrieving the C-style error code * but the opposite is now ''discontinued'' : Exceptions ''do not set'' the error flag anymore
2023-10-01 20:11:45 +02:00
TEST "Exceptions and Error flags" ExceptionError_test <<END
link tests with stringent application scope dependencies (closes #938) - the tests covering threadind support and object monitors are located in the backend test-library and linked against liblumierabackend.so - some fundamental facilities of proc-layer moved from the library tree into the basic components tree, since *testing* them requires at least to link against liblumieracommon.so
2014-10-17 21:15:59 +02:00
out: caught: LUMIERA_ERROR_LIFE_AND_UNIVERSE:and everything\? \(don't panic\)...the answer is: 42
out: caught lumiera::Error: LUMIERA_ERROR_DERIVED:convoluted exception
out: caught error::Logic: LUMIERA_ERROR_FATAL:floundered \(test-2\).
out: caught error::Invalid: LUMIERA_ERROR_INVALID:invalid input or parameters \(test-3\).
out: caught lumiera::Error: LUMIERA_ERROR_EXTERNAL:failure in external service \(test-4\).
out: caught std::runtime_error: test-5
out: caught std::exception. \(unspecific\)
out: intermediate handler caught: LUMIERA_ERROR_EXTERNAL:failure in external service \(test-7\).....will rethrow as error::State
out: caught lumiera::Error: LUMIERA_ERROR_STATE:unforeseen state -- caused by: LUMIERA_ERROR_EXTERNAL:failure in external service \(test-7\).
out: intermediate handler caught: LUMIERA_ERROR_EXTERNAL:failure in external service \(test-8\).....will rethrow as error::State
out: 2nd intermediate handler caught: LUMIERA_ERROR_STATE:unforeseen state -- caused by: LUMIERA_ERROR_EXTERNAL:failure in external service \(test-8\).....will rethrow as error::Config
Modernise Unknown Exception handler and Exception messages
2018-04-02 01:48:51 +02:00
out: caught error::Invalid: LUMIERA_ERROR_CONFIG:misconfiguration -- caused by: LUMIERA_ERROR_EXTERNAL:failure in external service \(test-8\)\.
link tests with stringent application scope dependencies (closes #938) - the tests covering threadind support and object monitors are located in the backend test-library and linked against liblumierabackend.so - some fundamental facilities of proc-layer moved from the library tree into the basic components tree, since *testing* them requires at least to link against liblumieracommon.so
2014-10-17 21:15:59 +02:00
out: caught lumiera::Error: LUMIERA_ERROR_LIFE_AND_UNIVERSE:and everything\? \(what is the answer\?\)\.
test-suite: fix lots of missing return value checks without that check, in theory our test runner will tolerate a non-zero return value, like throwing or failing an assert, which is not what we want.... guess these happenend to get in by forgetting to add this check when switching a test from PLANNED to TEST
2016-01-28 22:30:24 +01:00
return: 0
link tests with stringent application scope dependencies (closes #938) - the tests covering threadind support and object monitors are located in the backend test-library and linked against liblumierabackend.so - some fundamental facilities of proc-layer moved from the library tree into the basic components tree, since *testing* them requires at least to link against liblumieracommon.so
2014-10-17 21:15:59 +02:00
END
Reference in a new issue Copy permalink