Note that the command was

./pants

, running v1 tasks...

Pants V1 still runs V2 code for build file parsing and target creation

It got past that and started running tests

so, i repro this for

./pants test contrib/go/tests/python/pants_test/contrib/go/tasks

, but it looks specific to the test harness. it’s the “inner” pants that is under test that experiences this, and not the outer pants. and moreover, if you hit

lsof

on the subprocess, you can see that it is a plain jane “we’ve opened hundreds of Schedulers for some reason” case, and we do actually hit a 10k limit about halfway through the test.

Huh. Remember that Alex used to hit this all the time? The solution was to make the scheduler set up be per class, rather than per test

that test target contains about 8 files and 10 total instances of

TestBase

. but 10 schedulers shouldn’t be enough to hit these limits.