PR# 19292 How to remove an auto test?

Problem Report Summary
Submitter: uwindl
Category: EiffelStudio
Priority: Medium
Date: 2016/11/16
Class: Feature Request
Severity: Non-critical
Number: 19292
Release: 16.05
Confidential: No
Status: Analyzed
Responsible: jfiat_es
Environment: linux
Synopsis: How to remove an auto test?

While examining an AutoTest problem, I added a new dummy test. After that I found out that there is no way (or I found none) to remove a test from AutoTest.
After removing the corresponding file of the unneeded AutoTest (and recompiling), EiffelStudio (actually "ec") hung with 100% CPU usage on a single core when being asked to perform the AutoTests. While doing so, the GUI of EiffelStudio was not responding to any mouse interaction; specifically I could not stop the AutoTest.
Hunting for the problem (via strace), I saw many SIGSEGV that seemed to be handled internally, so the user never saw them. Maybe that was the reason for 100% CPU usage.
At some point I saw this message that might indicate some runtime-library-related problem:
ec: PANIC: signal stack overflow ...

ec: system execution failed.
Following is the set of recorded exceptions.
NB: The raised panic may have induced completely inconsistent information:
(There was no more output)
Removing a single AutoTest should be as easy as adding one. Going via is not very obvious (it's hard to find intuitively).
To Reproduce
Try to remove an AutoTest previously added.
Problem Report Interactions
From:jfiat_es    Date:2017/03/27    Status: Analyzed    Download   

To remove an autotest , as you found out, you can remove the related file, or if you want to remove on test in that class, just delete the related code.
However this is not intuitive, so we'll see how to make it easier from the IDE to remove an auto test.

Now about the issue you experienced, we were not able to reproduce it with EiffelStudio 17.01 (latest release) and 16.05 , on Windows or Linux.
Are you able to reproduce it easily ?
If yes, can you, please, provide us either with an archive of a small system that exhibits this issue, or with more details to reproduce it?