Ben Boeckel
Ben Boeckel
Manual testing (sorry for the hijack): Do: check
Do: check
VTK does [here](https://gitlab.kitware.com/third-party/loguru). If you mean an *actively maintained* fork…not sure where that would come from. I'm fine with picking patches into VTK's tracking branch as long as upstream is...
Sounds like something in the vein of `nextest` then, no?
Note that I found patches in other projects importing the script; I'd like to sync with those first before merging.
I believe that #445 is far more elegant for this. What do you think?
Hmm, ok. I'll take a look at `extras`. It's looking promising. Thanks.
Interestingly, I have kind of the reverse issue. I'm running a CI job under `arch -x86_64` (since Intel machines are getting towards EOL and we need "oompf" to carry Intel...
I'll try to keep an eye out for it. Luckily the project is low-traffic and it uses its own build directories. It may be difficult due to the meson `pyproject.toml`...
It happened again! [CDash logs](https://open.cdash.org/builds/10766976/notes#5634538) ``` ninja: Entering directory `build' [1/961] Generating src/compiler/glsl/float64_glsl.h with a custom command [2/961] Generating src/compiler/glsl/glcpp/glcpp-parse.[ch] with a custom command [3/961] Generating src/mesa/program/program_parse_tab.[ch] with a custom...