You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that when a test fails because of a segmentation fault, it causes the whole testing framework to bug out since runtime fails to cleans itself properly.
For example, after restarting my docker and running a test that works, I'll uncomment a previously uncommented block of code that is intended to fail -> raises a seg fault. After the seg fault is raised and the test fails, I'll re-comment out the buggy block of code and run the test again -> the test that previously worked now fails.
I was thinking that we force runtime to clean itself preemptively when calling start_test(). Any thoughts on this?
The text was updated successfully, but these errors were encountered:
benliao1
changed the title
Testing Framework Issues -- Segmentation Faults
[TEST] Testing Framework Issues -- Segmentation Faults
Jun 22, 2023
I've noticed that when a test fails because of a segmentation fault, it causes the whole testing framework to bug out since runtime fails to cleans itself properly.
For example, after restarting my docker and running a test that works, I'll uncomment a previously uncommented block of code that is intended to fail -> raises a seg fault. After the seg fault is raised and the test fails, I'll re-comment out the buggy block of code and run the test again -> the test that previously worked now fails.
I was thinking that we force runtime to clean itself preemptively when calling start_test(). Any thoughts on this?
The text was updated successfully, but these errors were encountered: