fix(79): Ensure tests supposed to fail also fail, when monitoring is disabled (--no-monitor cmd flag)

[lhpt2]

Description

There was a bug that resulted in some tests not failing when the cmd flag --no-monitor is set. Raising a BaseException in the corresponding code that runs when monitoring is disabled (line 218 following) solves the issue.

Fixes #79

fix(79): Ensure test supposed to fail also fail, when monitoring is disabled (--no-monitor cmd flag)

changelog updated in this commit too

The issue was an exception not being raised when calling wrapped_function when monitoring is disabled in line 216. The raise is being handled now in the following lines 218ff.

• [x] Bug fix (non-breaking change which fixes an issue)

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code ~- [ ] I have commented my code, particularly in hard-to-understand areas~ ~- [ ] I have made corresponding changes to the documentation~
• [x] My changes generate no new warnings ~- [ ] I have added tests that prove my fix is effective or that my feature works~ ~- [] New and existing unit tests pass locally with my changes (not just the CI)~ ~- [ ] Any dependent changes have been merged and published in downstream modules~
• [x] I have provided a link to the issue this PR adresses in the Description section above (If there is none yet, create one !)
• [x] I have updated the changelog
• [ ] I have labeled my PR using appropriate tags (in particular using status labels like Status: Code Review Needed, Business: Test Needed or Status: In Progress if you are still working on the PR)

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
30.6% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[lhpt2]

I'm not sure what SonarClouds wants to say with DuplicationOnNewCode or how I could resolve that.

[lhpt2]

The newest commit is a bug fix introduced by the memory_profiler module, which doesn't catch all Exceptions (only checks for Exception not BaseException). Worked around this by returning the exception from the wrapped function. This is only a temporary workaround to make everything work, it should be considered to do it as in PR #82 and replace the whole memory profiler module in some way and fix the issues that way. The bug occurs on test runs and causes them to not finish but block execution from finishing.