Give the ES test-suite enough time to run
The watchdog timer's usual 5 minutes is roughly how long the test takes to run (and it gets run twice), so there's a good chance of timing out. Avoid flakiness by giving it a third as much again on top of the default. Change-Id: I7cc9e392ab939ffe45d92bde635433d272e17388 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
This commit is contained in:
parent
127659c450
commit
ab6cfcfe84
|
@ -8,6 +8,14 @@ DEFINES += SRCDIR=\\\"$$PWD\\\"
|
|||
TESTSCRIPT=$$PWD/test262.py
|
||||
isEmpty(V4CMD): V4CMD = qmljs
|
||||
|
||||
# The ES test suite takes approximately 5 mins to run, on a fairly
|
||||
# vanilla developer machine, so the default watchdog timer kills the
|
||||
# test some of the time. Fix by raising time-out to 400s when
|
||||
# invoking tst_ecmascripttests:
|
||||
checkenv.name = QTEST_FUNCTION_TIMEOUT
|
||||
checkenv.value = 400000
|
||||
QT_TOOL_ENV += checkenv
|
||||
|
||||
checkjittarget.target = check-jit
|
||||
checkjittarget.commands = python $$TESTSCRIPT --command=$$V4CMD --parallel --with-test-expectations --update-expectations
|
||||
checkjittarget.depends = all
|
||||
|
|
Loading…
Reference in New Issue