Paul O'Leary McCann

Thanks for all the feedback! I had been focused on testing the training part, but it looks like there was a lot of cleanup left. I am doing a test...

My test run of training and evaluation with the above changes finished successfully.

Just a warning, but since the components are in experimental now, I'm going to move this from `pipelines` to `experimental`, which will be disruptive if you have a local copy.

The test I just added is failing in CI - the logs aren't clear, but I think it's just an issue of requirements not being installed in the test env....

The previous test failures were due to GPU-related issues. Those are resolved but this is still failing, and I think it's due to disk space related issues (like the strange...

After debugging, I'm still not 100% sure what exit code -9 means, but it looks like this might be an issue with memory and not disk usage. I've changed the...

Test works now, so that should make sure this runs on Windows. One thing that came up during the test is that this repo uses env vars to set overrides...

That's correct, it's running with tok2vec on CPU. That's partly because there's no GPU instance, and partly to keep memory and disk usage down so that the job doesn't die...

Going to close and re-open to pull in latest changes in experimental PR...

It looks like the tests are failing on Linux due to memory usage when training the SpanResolver. None of the recent changes should modify that so maybe it's just flaky,...