https://llvm.org/bugs/show_bug.cgi?id=25063
Todd Fiala <todd.fi...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Todd Fiala <todd.fi...@gmail.com> ---
On the OS X side, the issue is that we start the processes suspended, which
puts them in a state that the kernel will absolutely refuse to service signals
for --- it is really not running yet.
I thought about adding a clean-up step in the test runner that scans for
process group members that are not yet dead at test exit, and if a hard kill
doesn't take care of them, then use the in-test-runner-process lldb module to
attach and then kill, since this is all that is really needed. But rather than
add that complication, I went with taking care of the core issue, which is
doing too much all at once in a parallel test runner environment. I could have
tried to calculate the number based on # cores, but that's not really good
enough. So for now I cut it from 50 to 20 after talking to Jason Molenda about
it. This is plenty to stress what was desired to be stressed at the time the
test was written.
Change to # concurrent debuggers made here:
svn commit
Sending test/api/multiple-debuggers/multi-process-driver.cpp
Transmitting file data .
Committed revision 249421.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
