diff options
| author | Mike Kaganski <mike.kaganski@collabora.com> | 2021-06-08 21:32:54 +0300 |
|---|---|---|
| committer | Mike Kaganski <mike.kaganski@collabora.com> | 2021-06-08 23:27:06 +0200 |
| commit | 3bcaa4ba79477a21251ddaa06e0ea159196a7ffb (patch) | |
| tree | 745401894369ee99ea701d902891a567745412cd /solenv | |
| parent | dac70b9debb7c68def456ae90463ef6ced44c07d (diff) | |
Unset TZ when starting UITests on Windows
This workarounds a problem that some tests in trackedChanges.py fail on Windows
in specific time spans, at least in Europe/Moscow time zone: the change date in
the dialog is reported according to local system time, while the expected date
string is created in Python wrong, likely because datetime.datetime.now in the
native Windows Python takes into account both system timezone data and the TZ
environment variable coming from Cygwin (or some other kind of Python bug). The
time reported by datetime.datetime.now was off by -2 hours, and resulting date
string was wrong from 00:00 till 02:00.
See upstream bug at https://bugs.python.org/issue44352.
Change-Id: Ife3bcf000acac37f624a1065512513cc41dae596
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/116862
Tested-by: Mike Kaganski <mike.kaganski@collabora.com>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
Diffstat (limited to 'solenv')
| -rw-r--r-- | solenv/gbuild/UITest.mk | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/solenv/gbuild/UITest.mk b/solenv/gbuild/UITest.mk index 92eaaf9faefb..0a08939239b8 100644 --- a/solenv/gbuild/UITest.mk +++ b/solenv/gbuild/UITest.mk @@ -76,6 +76,7 @@ else TestUserDir="$(call gb_Helper_make_url,$(dir $(call gb_UITest_get_target,$*)))" \ PYTHONDONTWRITEBYTECODE=0 \ $(if $(ENABLE_WERROR),PYTHONWARNINGS=error) \ + $(if $(filter WNT,$(OS)),TZ=) \ $(gb_TEST_ENV_VARS) \ $(gb_UITest_COMMAND) \ --soffice="$(gb_UITest_SOFFICEARG)" \ |