Ben Evans

So we recently renamed the defunct `test_summary` folder in the main repo to `output` so that there is a known, useable folder in the repo that VSCode can automatically use...

I agree - a level of abstraction by using an environment variable makes it all a lot clearer, more uniform and much more flexible.

This does not appear to be a problem when testing on `noble`, although 13 tests are currently failing.

Hmm, they all passed when running with a single core! Perhaps there's a race condition somewhere?

I've just built a new `chaste/release` image (based on the latest `ubuntu:noble` image with chaste `2024.1` compiled) and run the tests with a single core (on `arm64`) and this is...

Yes, that's right. Naturally the default behaviour can be changed to e.g. a bash prompt or it can be overridden as desired on any given run by passing the command...

I think this is ready to review. One last refinement would be to somehow get the version from pypi or the repository and tag the image with it (in addition...

> > One last refinement would be to somehow get the version from pypi or the repository and tag the image with it (in addition to `latest`) so that there...

> Hi @bdevans. I had a closer look and I agree we are almost there. I played around a bit with the docker file and there are a few minor...

> Um, regarding my proposal of building the wheel outside the docker build process: how does the `buildx` with the two platforms actually work in practice? Will it run the...