Skip to content

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

@srajadnya1

Description

@srajadnya1

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions