On Fri, 18 Jul 2025 at 10:16, Bertho Stultiens <l...@vagrearg.org> wrote:
> That is interesting. So, why/how does mb2hal exit... I think that halrun -f always exits once the HAL file is parsed unless the -I (interactive) flag is set: https://linuxcnc.org/docs/stable/html/man/man1/halrun.1.html "If a filename is specified and neither the -I nor the -T option ... After processing, the realtime environment will be torn down." > But this does not resolve the race. For that you need to be sure that > mb2hal exited /before/ you run the checkresult diff. Maybe it should > simply test whether it is still alive I was wondering about something along those lines, but was actually (after some web searching) looking at using lsof to wait for the "result" file to be closed. But I am also wondering if that check should be in the "runtests" script rather than in specific "checkresults" scripts. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
