Frédéric Simonis

Are you referring to the version prior to the [rewrite that came with 3.10](https://gitlab.kitware.com/cmake/cmake/merge_requests/893) or in general?

@jedbrown Fair enough. The error message is misleading though as the tests fail due to the missing include and not a faulty PETSc install. The root of the problem is...

Noteworthy is the upgrade of `jekyl-sass-converter` to version 2. They switched from `Ruby Sass` to `csass`, as the former has __reached end-of-life__: ``` Post-install message from sass: Ruby Sass has...

An alternative would be to create and extract the cache relative to the working directory. This way, both workflows use a single cache.

For reference, the closest I could come up with is conditionally attaching a fixture to the master suite in my custom `unit_test_init()`: ```cpp if (condition) { struct GoBoom { GoBoom()...

After some cleanup of our test setup, I was able to implement this using a global fixture. I'll still describe my use-case even though it is a bit exotic. ###...

We could use [this test case](https://github.com/precice/aste/tree/mapping-tests/contrib/turbine).

@quentonwu Thank you for the comment! The (your?) blog post mentions preCICE version `1.3.0`. Which version are you currently using? This issue should be fixed with https://github.com/precice/precice/pull/686 which was released...

We could use build the vm with precice installed in `/usr/local` (default).

So, the real fix would be to use `-j` without argument and let the user specify an amount if necessary. Also keep in mind that `-j` will compile faster on...