ocean kraken
The first getting started guide for the Go SDK used Go's parallelism to build a matrix. Then it was updated to make use of the engine's natural parallelism by adding each build's output into a common output directory and later calling a single .Export() on that dir.
In the Python SDK's guide, instead of a build (which produces an artifact), it runs tests (no artifact). I'm interested in seeing if the same pattern for the Go guide makes sense here. I can add each command's .stdout() (which is a File) as the artifact, but in this case it doesn't make sense to .Export().
Is there something else that makes more sense in this use case?