|
From: Geoff B. <geo...@gm...> - 2023-11-21 12:36:38
|
Hi John! 1) There is a config setting "kill_timeout" which would explain this behaviour, basically terminating the test after 5 minutes. Have you set that in your config file(s) to 300, i.e. 5 minutes? Possibly copied it from a previous one without noticing it was there? https://texttest.sourceforge.net/index.php?page=documentation_4_3&n=running_texttest_unattended#kill_timeout 2) I don't think the stack smashing detected message has anything to do with this issue. At least I am seeing this frequently when closing TextTest these days. Unfortunately it seems to be some issue with newer versions of PyGObject, the UI library that TextTest uses. I recommend to add the following text to your config file: suppress_stderr_text:stack smashing detected which will get rid of it in all circumstances. Regards, Geoff On Tue, Nov 21, 2023 at 1:29 PM John Rydén <Joh...@ou...> wrote: > Hi! > > We're using texttest to do a test that is expected to take up to 1h to > carry through. > We're using Sikuli to perform the necessary steps in the application. > The problem is that after about 5 minutes into the test it aborts with an > error message: "*** stack smashing detected ***: terminated". > > Is there something inherent in the framework that prevents doing long-run > tests like this? > > Kind regards > John > _______________________________________________ > Texttest-users mailing list > Tex...@li... > https://lists.sourceforge.net/lists/listinfo/texttest-users > |