regression: CMake 3.27.x: Fortran: Ninja module dependencies
!8645 (merged) partly fixed this issue introduced in CMake 3.27.0. But for many Fortran projects, CMake 3.27.0..3.27.4 is still broken in a project with multiple Fortran modules interdependent, which is quite common.
I have made a Gist illustrating this issue that happens across any compiler, operating system, etc. Depending on number of CPU cores i.e. Ninja workers, the build errors result. To reproduce I run cmake --build build --clean-first
a few times. For laptop with 8 CPUs or a workstation with 64 CPUs, build errors happen almost 100% of the time.
Again while CMake 3.27.1 made the issue happen less frequently by chance, depending on number of Ninja parallel workers etc. it is still happening too often such that we are forced to use CMake 3.26.5 on our Fortran projects.