Problem:

In the process of testing the calculator I noticed that sometimes some unexpected behavior happened in a way that if I ran the app X times, in something around 8% of the cases the tests failed. Down below there is some tests that I had done to check that correctly:

Error checking:

Here I just ran the calculator tests some hundreds of times and stored the output into a file:

for x in {0..200}; do ./build/calc -t >> loop_analysis.txt; done

Which, after some text parsing, generated a file just as like I got something like this:

Succeeded!
Succeeded!
Succeeded!
Succeeded!
Succeeded!
Succeeded!
Succeeded!
Succeeded!

Succeeded!
Failed! (code 11)
Failed!
Failed!
Succeeded!
Failed!
Succeeded!
Succeeded!
.
.
.

So I used grep to count how much errors did I get, and got this:

echo "Succeeded: " && grep -c "Succeeded" loop_analysis.txt && echo "Failed: " && grep -c "Failed" loop_analysis.txt

Succeeded: 
1454
Failed: 
154

So certainly this is in some way getting some undefined behavior at some point that i'm not sure.

The expected behavior would be to have consistent and successful test results without any intermittent failures.

Request

I'm seeking assistance in resolving these intermittent test failures. I've tried to isolate the issue and attempted basic debugging, but the root cause remains elusive. It could potentially unexpected inputs, or other factors triggering this behavior.

Could someone proficient with debugging and testing help investigate and correct this issue properly? Any insights, suggestions, or debugging tips would be greatly appreciated.

Thank you for your help!