-
-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pantsd nailgunerror segfault #6714
Comments
There is just not enough to go on here. The only fishy looking thing is:
And its only fishy because it has the last two stack lines being the same - which doesn't make sense generally or even specifically looking at line 1404 of pkg_resources/_vendor/pyparsing.py in setuptools-40.4.3. I'd say there is much more digging to do. |
lldb backtrace on the stopped thread:
|
EXC_BAD_ACCESS in libdispatch.dylib suggests to me that this is a fork-safety issue. I believe that libdispatch starts up background threads, which makes it unsafe to use when we fork and don't exec. |
#7323 might be a dupe of this one. |
### Problem Due to pantsbuild/pants#6714, and maybe pantsbuild/pants#7323, the OSX 12 shard frequently flakes when Pantsd is enabled, as seen [here](https://travis-ci.org/pantsbuild/setup/jobs/507257503#L432), [here](https://travis-ci.org/pantsbuild/setup/jobs/507238744#L545), and [here](https://travis-ci.org/pantsbuild/setup/jobs/507238744#L681). This blocks #32, as that PR will result in each shard running with Pantsd a total of 6 more times, which results in an almost certain guarantee at least one shard will flake. ### Solution Temporarily skip pantsd tests for OSX 10.12. We do not completely remove the shard, as the first two tests still work and are useful to include.
Closed via #7596! |
When attempting to run pants commands in our local repo, I encounter this error:
This resolves as soon as I turn the daemon off. The exceptions.log and PEX-INFO is attached. Also, important to note that this currently occurs only on osx 10.12. osx 10.13 and above do not exhibit the issue afaik.
exceptions (1).log
PEX-INFO (1).txt
The text was updated successfully, but these errors were encountered: