Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Oh, and I think turning on ldebug might have caused it to stop failing for Stu's change

I do see an odd traceback in the stdout during the test tho

```                     executed 188 nodes in 1947 scheduling iterations. there have been 6238 total steps for 1361 total nodes.
                     Traceback (most recent call last):
                       File "/usr/lib64/python2.7/multiprocessing/util.py", line 274, in _run_finalizers
                         finalizer()
                       File "/usr/lib64/python2.7/multiprocessing/util.py", line 207, in __call__
                         res = self._callback(*self._args, **self._kwargs)
                       File "/home/kw/pants-release/.pants.d/python-setup/chroots/0cc20d95442fe9cce1c31697c8836191ee39d6fd/.deps/cov_core-1.15.0-py2-none-any.whl/cov_core.py", line 19, in multiprocessing_finish
                         cov.stop()
                     AttributeError: 'NoneType' object has no attribute 'stop'
                     Traceback (most recent call last):
                       File "/usr/lib64/python2.7/multiprocessing/util.py", line 274, in _run_finalizers
                         finalizer()
                       File "/usr/lib64/python2.7/multiprocessing/util.py", line 207, in __call__
                         res = self._callback(*self._args, **self._kwargs)
                       File "/home/kw/pants-release/.pants.d/python-setup/chroots/0cc20d95442fe9cce1c31697c8836191ee39d6fd/.deps/cov_core-1.15.0-py2-none-any.whl/cov_core.py", line 19, in multiprocessing_finish
                         cov.stop()
                     AttributeError: 'NoneType' object has no attribute 'stop'
                     PASSED```

I think probably.  That's when ldebug is turned on

Repros on the commit before my lock change

Okay, definitely repros pre-lock change too

At this point I'm stumped and I don't think it's a locking issue, at least not a recent one

`tests/python/pants_test/engine/test_engine.py`

`tests/python/pants_test/engine/exp/test_engine.py`

still seems intermittent - I just eek’d a pr across the line

cant distinguish any differences in the failing vs working envs

which specific test? where to look at the logs

yeah, on <https://travis-ci.org/pantsbuild/pants/builds/121002400>

We don't know--we can't get it to repro with ldebug on