Kiwi test suite hangs indefinitely in KWSymbolicator while waiting for /usr/bin/atos

[sharplet]

Xcode 6.1.1, OS X 10.10.2

I noticed that the tests seemed to be taking a long time to start up on my machine, and when I paused in the debugger the test suite was stuck waiting for the NSTask calling out to /usr/bin/atos to complete.

If I run the command directly via the shell it completes and prints the expected output, so maybe this is something to do with the use of NSTask when running in the iOS Simulator? The tests run fine against Mac OS X.

If you happen to have any thoughts on this @jerrymarino, I'd appreciate it!

[jerrymarino]

Hey @sharplet, it looks like Yosemite has changed a few things around symbolication and making calls to atos.

The feature uses atos to find the physical line of a given call site so it can filter nodes based on the user specified KW_SPEC environment variable.

I tested it out in Yosemite it it seems to deadlock. However, I can successfully symbolicate with atos for a given process id if I invoke atos via external shell which is a good sign. I've got a few ideas of how to fix this in Yosemite and will have bandwidth to dig into it this weekend or next.

I know focused tests are important: when working with a decent sized test suite it's a huge time saver. I hear from many people the Xcode plugin is helpful and needs Yosemite & Xcode6 support.

From what I remember, it can get laggy when dealing with a large KWSpecs. I have a good idea of how to get constant time performance on the calls to atos (i.e. O(1) symbolications :) )

It might be the right call to disable the feature for 10.0 until we have a fix.

[jerrymarino]

Hey @sharplet I tested the fix out in 10.10.2. Xcode 6.1.1 and it seemed to work well.

From my empirical testing, it seems that in the latest versions of OSX & Xcode it's not possible to run atos from the simulator with the pid. It just hangs. I tested the command out in an external shell and it still worked. The workaround is to just use the executable path instead of the pid (via the -o argument).

I think launching the task in the background and setting a timeout is more user friendly than just waiting indefinitely for it to exit ala -[NSTask waitUntilExit]. If atos doesn't work in the future (times out, doesn't launch, or fails) the error messages should be somewhat helpful. 🍻

[ecaselles]

@jerrymarino 👏

[sharplet]

Fixed in #597.