Hi, what do you mean by “The time to run in 1, 2 or 4 is the same for us”? Are you talking about timing of running parallel container or an issue with one of your commands?
I noticed you clicked like on the last comment, so I’m assuming that’s the issue you’re referring to. I think they’re describing the situation in this support article. Where you’ve run your tests in parallel containers and you need to combine them into a single results file. There’s no automatic way to do that as far as I know. You’ll need to do what the support article describes. Create a “collection” job that is connected to the parallel job through a workspace. When all of the parallel jobs are complete they will pass the test result files to the collection job through the workspace. Just make sure that you’re naming the file something different during the parallel run.
I didn’t actually test that config so you might need to rework it a bit. But you’ll notice within the test-output file name for pytest I’m using CIRCLE_NODE_INDEX like:
This will make sure all the test file outputs have a unique name when they’re persisted to the workspace.
When the downstream job runs it will attach the workspace to a folder called test-results, and all of the different test output files from the parallel runs will be available.
From here you could combine them in some way if you need to, or process them individually. There’s no automatic way to combine them. But there are some tools available that might be able to help. Is that the result you’re looking for?