Seems that the vsts-task-lib findMatch method we are using to locate the report-task.txt is broken when there are too many files in the workspace.
I reported upstream, but maybe we could use another way to locate the file.
UPDATE: there is a PR open in the Microsoft/azure-pipelines-task-lib to fix the issue (opened since March 15th 2019).
UPDATE: the MS fix has been merged and will be released in azure-pipelines-task-lib v3.1.0. Note that this is a somewhat newer version of the task library than we are using so we'll need to check that it doesn't impact the versions of VSTS we support (we are currently using firstname.lastname@example.org i.e. one major release from before the VSTS to Azure DevOps rename).
Reported by community: https://community.sonarsource.com/t/gc-overhead-limit-exceeded-using-the-vsts-task/2528
Another report: https://community.sonarsource.com/t/vsts-publish-quality-gate-result-with-npm-parses-node-modules-folder-and-hangs-on-symbolic-links/7058