Unexpected fault during test does not cause test failure

[pizi-nordic]

Describe the bug
Faults during tests are not treated as test failure:

(...)
starting test - test_mutex_lock_timeout                 
***** MPU FAULT *****                                   
  Data Access Violation                                 
  MMFAR Address: 0xe                                    
***** Hardware exception *****                          
Current thread ID = 0x20000468                          
Faulting instruction address = 0xfbbc                   
Fatal fault in thread 0x20000468! Aborting.             
PASS - test_mutex_lock_timeout                          
========================================================
starting test - test_semaphore                          
PASS - test_semaphore                                   
========================================================
starting test - test_mempool                            
***** BUS FAULT *****                                   
  Imprecise data bus error                              
***** Hardware exception *****                          
Current thread ID = 0x20000518                          
Faulting instruction address = 0xf942                   
Fatal fault in thread 0x20000518! Aborting.             
PASS - test_mempool                                     
(...)
===================================================================
PROJECT EXECUTION SUCCESSFUL

To Reproduce
Trigger unexpected fault during test.

Expected behavior
Any unexpected fault should result in test failure.

[nashif]

this type of failures is caught when run in sanitycheck, when we run those tests on the command line there is no way to capture those exceptions, unless the test actually fails because of them.
Sanitycheck on the other hand looks for those exceptions and fails the test even if it reports success.