Closed Bug 1192962 Opened 11 years ago Closed 8 years ago

When running talos locally, ctrl+c doesn't do a clean kill

Categories

(Testing :: Talos, defect)

Product:
Testing
Component:
Talos
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: kats, Unassigned)

References

Details

(Whiteboard: [talos_wishlist])

On OS X m-c, run: ./mach talos-test chromez-e10s After the window opens, try to terminate the test by running ctrl+c in the console. Expected: everything shuts down Actual: something keeps running in the background and so new firefox windows keep spawning and resizing themselves. I had to do "ps" to find the thing that was running and kill it. I observed similar behaviour when running svgr.
I suspect this is mach killing the current talos test and then it starts up on the next test in the list. chromez runs 2 tests, svgr runs a few more.
Blocks: 1088251
Whiteboard: [talos_wishlist]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.