Re: Problem when configure.py is run simultaneously

2017-08-07 Thread Scott Kostyshak
On Tue, Aug 08, 2017 at 02:22:46AM +0200, Kornel Benko wrote: > Am Montag, 7. August 2017 um 19:32:15, schrieb Scott Kostyshak > > > On Mon, Aug 07, 2017 at 09:36:34AM +0200, Kornel Benko wrote: > > > Am Sonntag, 6. August 2017 um 21:55:57, schrieb Scott Kostyshak > > > > > > > On Sun, Aug 06,

Re: Problem when configure.py is run simultaneously

2017-08-07 Thread Kornel Benko
Am Montag, 7. August 2017 um 19:32:15, schrieb Scott Kostyshak > On Mon, Aug 07, 2017 at 09:36:34AM +0200, Kornel Benko wrote: > > Am Sonntag, 6. August 2017 um 21:55:57, schrieb Scott Kostyshak > > > > > On Sun, Aug 06, 2017 at 10:17:16AM +0200, Kornel Benko wrote: > > > > > > > This should n

Re: Problem when configure.py is run simultaneously

2017-08-07 Thread Scott Kostyshak
On Mon, Aug 07, 2017 at 09:36:34AM +0200, Kornel Benko wrote: > Am Sonntag, 6. August 2017 um 21:55:57, schrieb Scott Kostyshak > > > On Sun, Aug 06, 2017 at 10:17:16AM +0200, Kornel Benko wrote: > > > > > This should not happen. The check for the need of reconfiguration is done > > > at LyX.cp

Re: Problem when configure.py is run simultaneously

2017-08-07 Thread Kornel Benko
Am Sonntag, 6. August 2017 um 21:55:57, schrieb Scott Kostyshak > On Sun, Aug 06, 2017 at 10:17:16AM +0200, Kornel Benko wrote: > > > This should not happen. The check for the need of reconfiguration is done > > at LyX.cpp:1053 > > bool LyX::queryUserLyXDir(bool explicit_userdir) > > which i

Re: Problem when configure.py is run simultaneously

2017-08-06 Thread Scott Kostyshak
On Sun, Aug 06, 2017 at 10:17:16AM +0200, Kornel Benko wrote: > This should not happen. The check for the need of reconfiguration is done at > LyX.cpp:1053 > bool LyX::queryUserLyXDir(bool explicit_userdir) > which is called at LyX.cpp:921. > This call is guarded with fileLock(lock_file.c_s

Re: Problem when configure.py is run simultaneously

2017-08-06 Thread Kornel Benko
Am Sonntag, 6. August 2017 um 01:10:02, schrieb Scott Kostyshak > I usually do the following for running the ctests: > > ctest -j$( nproc ) > ctest --rerun-failed > > This has behaved robustly for a while. However, I've recently gained access > to a > server where I could run 64 jobs s

Problem when configure.py is run simultaneously

2017-08-05 Thread Scott Kostyshak
I usually do the following for running the ctests: ctest -j$( nproc ) ctest --rerun-failed This has behaved robustly for a while. However, I've recently gained access to a server where I could run 64 jobs simultaneously, and now the above approach shows problems, compared to results from