The problem with these files is that there is no warning.
In my case the error was that
Execute source Makefiles
failed but no error was generated at all.
The Makefile did not fail. There was just nothing to do, because of that the Makefile returned a code != 0.
What I expect is that make.sh checks for these lock files and exits with a warning that there are these lockfiles.
I did not look into the lockfiles, but if possible it would be cool to write user and hostname into this file. We are using them via a shared network mount.
The problem with these files is that there is no warning. In my case the error was that Execute source Makefiles failed but no error was generated at all. The Makefile did not fail. There was just nothing to do, because of that the Makefile returned a code != 0. What I expect is that make.sh checks for these lock files and exits with a warning that there are these lockfiles. I did not look into the lockfiles, but if possible it would be cool to write user and hostname into this file. We are using them via a shared network mount.