Veselin Dobrev

Re-running failed jobs.

Restarting again after fix in the gh-action.

> GCC build errors caused by an existing GCC bug demonstrated here https://godbolt.org/z/6eM7xT7xE > > https://stackoverflow.com/questions/68826162/gcc-and-clang-differs-in-behavior-when-calling-variadic-member-function-template > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77731 It looks like we need a workaround that works with GCC...

We should add `rm -rf libmjit*` to the `clean` targets in `examples/` and probably all other places where we build executables.

It looks like CMake does not install `mjit` while GNU make does.

Running the tests with JIT enabled with CMake, I get some failures: ```The following tests FAILED: 3 - sedov_tests_debug (Subprocess aborted) 13 - psedov_tests_debug_np=1 (Failed) 14 - psedov_tests_debug_np=4 (Failed) ```

It will be good to add at least one serial and one parallel test using examples/miniapps when JIT is enabled. For example, the tests can be to run `./ex1 -pa...

See #3343 for suggested doxygen updates to resolve this issue.

I tried the following runs with MFEM's `master` branch (42e979eb) and MUMPS 5.5.1: ``` mpirun -np 4 ex25p -o 2 -f 1.0 -rs 1 -rp 1 -prob 0 -mumps mpirun...

Without a way to reproduce the issue, I'm not sure how to debug it. One thing I can suggest is running with `valgrind`, or building and running with ASan, e.g....