On 07/05/2017 19:46, Kornel Benko wrote:
Do they fail if retested separately too?

I tested again just a couple of these, one was keeping failing, another one 
succeeded, but I had no time for a proper investigation. Also, AFAICR my laptop 
started buzzing or smth while the overall tests batch was running, I suspect 
some keypresses didn't really result in what they were supposed to (I wasn't 
looking at the screen in that very moment), likely the cause of some of these 
failures.

I just tried removing the custom xvkbd from my dir (need the attached patch for 
that), and I've got this:

Running test cases . . .
                        bug-7673b-in.txt: Ok
                         bug-7673-in.txt: Ok
                         bug-8370-in.txt: Ok
                         bug-8482-in.txt: Ok
                         bug-8540-in.txt: Ok
                         bug-8684-in.txt: Ok
                 bug-export-latex-in.txt: Ok
                    bug-math-undo-in.txt: Ok
                       findadv-01-in.txt: Ok
                       findadv-02-in.txt: Ok
                       findadv-03-in.txt: Ok
                       findadv-04-in.txt: Ok
                       findadv-05-in.txt: Ok
                       findadv-06-in.txt: Ok
                       findadv-07-in.txt: Ok
                       findadv-08-in.txt: FAILED
                       findadv-09-in.txt: Ok
                       findadv-10-in.txt: Ok
                       findadv-11-in.txt: Ok
                       findadv-12-in.txt: Ok
                       findadv-13-in.txt: Ok
                       findadv-14-in.txt: FAILED
                       findadv-15-in.txt: Ok
                       findadv-16-in.txt: Ok
                       findadv-17-in.txt: Ok
                       findadv-18-in.txt: Ok
                       findadv-19-in.txt: Ok
                       findadv-20-in.txt: Ok
                       findadv-21-in.txt: FAILED
                    findadv-crash-in.txt: Ok
                     findadv-logo-in.txt: Ok
                    findadv-re-01-in.txt: Ok
                    findadv-re-02-in.txt: Ok
                    findadv-re-03-in.txt: FAILED
                    findadv-re-04-in.txt: Ok
                    findadv-re-05-in.txt: Ok
                    findadv-re-06-in.txt: FAILED
                 tabular-footnote-in.txt: Ok

There were 5 FAILED tests

However, I saw the buzzing this time: the new Ubuntu sends my screen dark 
earlier due to inactivity, and I start hearing these buzz, after entering my 
pwd, I saw the tests were still running, but I'm not sure they were affected by 
the screen saver ... need to check whether there's a way to prevent screen 
saver during these tests.

Which QT version?

5.7.1

        T.

diff --git a/development/autotests/run-tests.sh b/development/autotests/run-tests.sh
index 25d29340..23ab41cf 100755
--- a/development/autotests/run-tests.sh
+++ b/development/autotests/run-tests.sh
@@ -7,13 +7,13 @@
 export LYX_ROOT=../../..
 export LYX_EXE=$LYX_ROOT/src/lyx
 
-if [ "$XVKBD_HACKED" != "" ]; then
-    export XVKBD_EXE=${XVKBD:-./xvkbd/xvkbd};
-    if [ ! -x $XVKBD_EXE ]; then
-	echo "You need to build XVKBD first, try: cd xvkbd && xmkmf && make"
-	exit -1;
-    fi
-fi
+# if [ "$XVKBD_HACKED" != "" ]; then
+#     export XVKBD_EXE=${XVKBD:-./xvkbd/xvkbd};
+#     if [ ! -x $XVKBD_EXE ]; then
+# 	echo "You need to build XVKBD first, try: cd xvkbd && xmkmf && make"
+# 	exit -1;
+#     fi
+# fi
 
 if [ "$(which wmctrl)" == "" ]; then
     echo "You need to install wmctrl first, try:"
@@ -29,7 +29,7 @@ fi
 
 PROGRAM_SUFFIX=$(grep -e '#define PACKAGE ' ../../config.h | sed -e 's/#define PACKAGE "lyx\(.*\)"/\1/')
 
-export XVKBD_EXE=../$XVKBD_EXE
+export XVKBD_EXE=xvkbd
 export KEYTEST=../keytest.py
 LYX_HOME=out-home
 export LYX_USERDIR=$(pwd)/$LYX_HOME/.lyx$PROGRAM_SUFFIX

Reply via email to