You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing DICOM DateTime to epoch functionality
The next test should throw an error
ERROR: Time_Zone info '+020' does not fit DICOM standard
libc++abi: terminating due to uncaught exception of type std::runtime_error:
ERROR: Time_Zone info '+020' does not fit DICOM standard
This is pretty weird, at catch (...) should catch all exceptions AFAIK, so this seems like a clang bug to me.
Some tests check if errors are thrown. We caught any exception with
`catch (...)`. but that fails on OSX Clang 18. Now we catch
`std::runtime_error`, which is more accurate anyway.
FixesUCL#1490
Some tests check if errors are thrown. We caught any exception with
`catch (...)`. but that fails on OSX Clang 18. Now we catch
`std::runtime_error`, which is more accurate anyway.
FixesUCL#1490
You should now see an error about a wrong setting for alpha
ERROR: Alpha parameter for ramp has to be between 0 and 1 but is -1
libc++abi: terminating due to uncaught exception of type std::runtime_error:
ERROR: Alpha parameter for ramp has to be between 0 and 1 but is -1
We have a few tests that check if errors are thrown, e.g.
STIR/src/test/test_DateTime.cxx
Lines 105 to 114 in 209cbb6
However, with clang18 on MacOS these tests all fail
https://github.com/UCL/STIR/actions/runs/10450627407/job/28935385772?pr=1489#step:12:751
This is pretty weird, at
catch (...)
should catch all exceptions AFAIK, so this seems like a clang bug to me.However, we know what we're throwing
STIR/src/buildblock/error.cxx
Line 62 in 209cbb6
So we could just as well (or even better) catch
std::runtime_error
.The text was updated successfully, but these errors were encountered: