This is an archive of the discontinued LLVM Phabricator instance.

Allow test suite run to be interupted using ctrl-C.
AbandonedPublic

Authored by EricWF on Mar 18 2022, 9:49 AM.

Details

Reviewers
None
Group Reviewers
Restricted Project

Diff Detail

Event Timeline

EricWF created this revision.Mar 18 2022, 9:49 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 18 2022, 9:49 AM
Herald added a subscriber: arichardson. · View Herald Transcript
EricWF abandoned this revision.Mar 18 2022, 9:51 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 18 2022, 9:51 AM
Herald added a reviewer: Restricted Project. · View Herald Transcript
EricWF updated this revision to Diff 416535.Mar 18 2022, 9:54 AM

Not sure what Arc is asking

EricWF published this revision for review.Mar 18 2022, 9:57 AM

This sounds reasonable, but I'm curious -- can you describe what's the difference before and after the patch? Aren't we able to kill the test suite with CTRL-C right now?

[Github PR transition cleanup]

Gentle ping on this, I still don't understand how this changes the current behavior. I thought it was possible to use Ctrl-C right now?

EricWF abandoned this revision.Sep 8 2023, 10:23 AM

So the difference before and after is that if we ctrl-C during a long running tests, and the test catches it, it effectively swallows it.

This only becomes an issue when we're at the end of the test suite or when only 1 or two tests are running, because otherwise there's a good chance that all the worker threads are running C++ code, and none of them are currently executing pyython which will propagate the error.

I think I would rather actually replace subprocess.call with os.execve and simply replace the python process with the subprocess. However IDK if that's going to play nice on all platforms we care about.
I'll close this and submit a github PR.