Hi here, I’m trying to ship a few PRs (9226, 9227, 9228) but I’m getting no dice on the CI jobs: It seems that some of the python integration tests time out despite the changes affecting scala code. I tried re-running a few times without much luck. Here is an example subset of the output:

12:12:58 [INFO] Tests failed: contrib/awslambda/python/tests/python/pants_test/contrib/awslambda/python
12:13:16 [INFO] Tests failed: tests/python/pants_test/backend/python/tasks:python_repl_integration
12:13:24 [INFO] Tests failed: contrib/go/tests/python/pants_test/contrib/go/subsystems:integration
12:13:30 [INFO] Tests failed: tests/python/pants_test/projects:python_testprojects_integration
12:14:26 [INFO] Tests failed: tests/python/pants_test/backend/python/tasks:pytest_run_integration
12:14:57 [INFO] Tests failed: tests/python/pants_test/backend/python/tasks:python_run_integration
12:15:00 [INFO] Tests failed: tests/python/pants_test/core_tasks:substitute_target_aliases_integration
12:15:40 [INFO] Tests failed: tests/python/pants_test/backend/jvm/tasks:jvm_bundle_integration

(for instance https://travis-ci.com/pantsbuild/pants/jobs/293825763#L2946) Running

./pants test

for any of these targets locally seems to be fine (although I had to

./pants clean-all

first, apparently due to some weird interaction between the PEX upgrade and caching). Are we aware of what is causing this flakyness and do we know of any workaround. Alternatively, is there anything we could revert to make it easier again to contribute code to pants until the situation is improved?

moved to the #infra channel

Thanks. Sorry for the mis-chaneling

not a problem!!!

Yes, I kind of knew that. Just didn’t pay enough attention to where I was posting 🙂