Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TEST] Testing Framework Issues -- Segmentation Faults #259

Open
srajadnya1 opened this issue Apr 14, 2022 · 1 comment
Open

[TEST] Testing Framework Issues -- Segmentation Faults #259

srajadnya1 opened this issue Apr 14, 2022 · 1 comment

Comments

@srajadnya1
Copy link
Collaborator

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?

@benliao1 benliao1 changed the title Testing Framework Issues -- Segmentation Faults [TEST] Testing Framework Issues -- Segmentation Faults Jun 22, 2023
@benliao1
Copy link
Collaborator

Perhaps related to #179 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants