From 03116898b006b1c78ea82874fc12be29a4095696 Mon Sep 17 00:00:00 2001 From: Noel Grandin Date: Wed, 9 Jan 2019 12:03:30 +0200 Subject: [PATCH] update uitest debugging instructions to account for gtk3 backend issue e.g. when debugging UITest_writer_tests2 it gets stuck when the uitest invokes dialogs Change-Id: I8276a8d7e885be5f47309beeec1f4c3c9d12ee32 Reviewed-on: https://gerrit.libreoffice.org/66002 Tested-by: Jenkins Reviewed-by: Noel Grandin --- solenv/gbuild/uitest-failed-default.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/solenv/gbuild/uitest-failed-default.sh b/solenv/gbuild/uitest-failed-default.sh index e8646324bbad..4189f306a9ab 100755 --- a/solenv/gbuild/uitest-failed-default.sh +++ b/solenv/gbuild/uitest-failed-default.sh @@ -21,9 +21,12 @@ where Class - is the name in the "class Class" declaration Or to do interactive debugging, run two shells with: - make debugrun + SAL_USE_VCLPLUGIN=gtk make debugrun make gb_UITest_DEBUGRUN=T UITest_$2 +The SAL_USE_VCLPLUGIN part is unnecessary if you are running on a kde desktop. +(The default gtk3 backend has issues with some uitests). + Failing that, put a time.sleep(60) in the beginning of the method in the .py file,