Add workaround fix for faulty memory_profiler module

The memory profiler only reports Exceptions when it should report all
Exceptions that inherit from BaseExceptions.

This is ultimately reworked in a PR incorporating a simplified
memory profiler module into the codebase that fixes not only this issue
but also gives the possibility of getting measurements for failing
tests.

This workaround uses return values to work around the issue. This way
pytest-monitor can check for BaseExceptions and act accordingly.
Like described earlier the ultimate goal should probably be to replace
the whole memory profiler as proposed in this PR:
CFMTech#82

Author: Lucas Haupt

pytest_monitor/pytest_monitor.py

@@ -228,6 +228,13 @@ def wrapped_function():
         except Exception:
             raise
         except BaseException as e:
+            # this is a workaround to fix the faulty behavior of the memory profiler
+            # that only catches Exceptions but should catch BaseExceptions instead
+            # actually BaseExceptions should be raised here, but without modifications
+            # of the memory profiler (like proposed in PR
+            # https://github.com/CFMTech/pytest-monitor/pull/82 ) this problem
+            # can just be worked around like so (BaseException can only come through
+            # this way)
             return e
 
     def prof():
@@ -241,7 +248,14 @@ def prof():
         setattr(pyfuncitem, "monitor_results", True)
 
     if not PYTEST_MONITORING_ENABLED:
-        wrapped_function()
+        try:
+            # this is a workaround to fix the faulty behavior of the memory profiler
+            # that only catches Exceptions but should catch BaseExceptions instead
+            e = wrapped_function()
+            if isinstance(e, BaseException):
+                raise e
+        except BaseException:
+            raise
     else:
         if not pyfuncitem.session.config.option.mtr_disable_gc:
             gc.collect()