view .arcconfig @ 51955:b8528c8bebf5

tests: disable `worker.backgroundclose` to stabilize a test on Windows

TIL that `worker.enabled=0` doesn't prevent these workers from spinning up.  At
any rate, there's already a whole lot of conditionalized output following
`cat client.log`, the placement of the "starting 4 threads for background file
closing" message seems unstable, and we don't care about those worker threads
here.  Preventing the message is better for test maintenance.

{
    "conduit_uri": "https://phab.mercurial-scm.org/api",
    "phabricator.uri": "https://phab.mercurial-scm.org/",
    "repository.callsign": "HG",
    "arc.land.onto.default": "@",
    "base": "hg:.^"
}