Jerry Pussinen

I like the idea of having a "comment" but I think it should not live in the same level as the data for the tests. I guess the initial choice...

Good question! I tried it with my demo repo which uses GitHub Actions, I think they have 2 CPUs available. Seems to work nicely https://github.com/jerry-git/pytest-split-gh-actions-demo/pull/1. Here's the CI run: https://github.com/jerry-git/pytest-split-gh-actions-demo/runs/549132036....

@thedrow The demo project contains dummy tests which basically just sleep for a fixed number of seconds. Thus the results I explained are aligned with my expectations. @ethanhs That sounds...

@ethanhs I just cloned the mypy repo to see what's going on. So, I assume by "bare pytest" you mean pytest + pytest-xdist with `-nauto` option (uses all available cores...

@ethanhs I ran some experiments locally. I think it's not behaving well locally if `-n auto` is used for each group. If I distribute the work to CPUs based on...

I have macOS. I think it'd be interesting to do some trials with `mypy` test suite in a single machine environment in which there are no other heavy processes consuming...

Sounds great 👍 > while the other non-optional arguments would be the paths to the spilt durations files Does this mean that one would do something like `pytest-split-combine foo/split-1 foo/split-2...

FYI there's now a `slowest-tests` CLI command available. If someone wants to do the `pytest-split-combine`, the same idea can be used for introducing the CLI command, see e.g. https://github.com/jerry-git/pytest-split/pull/30

I haven't used CircleCI myself but this seems convenient indeed. However, I'm a bit hesitant about introducing some CI provider specific logic in a pytest-plugin. Wouldn't this be problematic if...

Yes indeed, a hook or similar might be the most flexible solution. If you have a solution in mind, feel free to create a patch (or update this one). This...