On Thu, Apr 4, 2013 at 7:23 AM, Kornel Benko <kor...@lyx.org> wrote: > Am Donnerstag, 4. April 2013 um 07:13:35, schrieb Scott Kostyshak > <skost...@lyx.org> > >> On Thu, Apr 4, 2013 at 7:00 AM, Kornel Benko <kor...@lyx.org> wrote: > >> > Am Donnerstag, 4. April 2013 um 12:32:19, schrieb Scott Kostyshak > >> > <skost...@lyx.org> > >> > > >> >> > >> > > >> >> commit 36da271b74784b77b54bfe2f0bc62624f9ce0345 > >> > > >> >> Author: Scott Kostyshak <skost...@lyx.org> > >> > > >> >> Date: Thu Apr 4 06:28:53 2013 -0400 > >> > > >> >> > >> > > >> >> Add test for #8370 (not yet fixed) > >> > > >> >> > >> > > >> > > >> > > >> > This test passes here. No new core-file around. > >> > >> Strange. When you follow the instructions manually can you reproduce? > >> http://www.lyx.org/trac/ticket/8370#comment:8 > > > > I can reproduce manually. Now there _is_ a core. And also > bug-8370.lyx.emergency, > > which was there from the automatic test too. We could check for the > existence > > of this file.
Yes, that seems like a good idea. It would also be nice to figure out why the tests are reporting as passed if they create a core and a .emergency file for you. From what I remember, the test returns failed if when it checks to see if LyX is still running, it is not (and thus it assumes a pre-mature exit). Can you try running the test with a pause after the crash should have been triggered? This should give some more time for LyX to disappear so that the test realizes it is gone and that the test should fail. If that's not the case, then I'm not sure what's going on. Somehow the LyX process must still be sticking around. Or at least the PID maybe? Scott
