suricata-verify: exceptions caused by code errors can be silently ignored
If you look the code change in this Suricata-Verify pull request, https://github.com/OISF/suricata-verify/pull/605/files, it looks like this should cause a runtime error as its calling a function that doesn't exist. However, in the exception handling this type of error is being silently absorbed.
The result is that tests that trigger this code path are not even displayed in the S-V output, and are not recorded as failures.
Ideally code errors like this should just have their exceptions raised to the top so the failure is spectacular.