wasm: enable JSPI when running tests on Chrome
Enable JSPI (aka asyncify 2). This allows building and running tests in that mode, which should faster and and is also compatible with wasm-exceptions. Change-Id: I76648de7dabd2297ab271385b45ff095f08b848e Reviewed-by: Piotr Wierciński <piotr.wiercinski@qt.io> Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
This commit is contained in:
parent
6643e97a89
commit
8d29622353
@ -666,7 +666,7 @@ function(qt_internal_add_test name)
|
||||
list(APPEND extra_test_args "--silence_timeout=60")
|
||||
# TODO: Add functionality to specify browser
|
||||
list(APPEND extra_test_args "--browser=chrome")
|
||||
list(APPEND extra_test_args "--browser_args=\"--password-store=basic\"")
|
||||
list(APPEND extra_test_args "--browser_args=\"--password-store=basic --enable-features=WebAssemblyExperimentalJSPI\"")
|
||||
list(APPEND extra_test_args "--kill_exit")
|
||||
|
||||
# Tests may require asyncify if they use exec(). Enable asyncify for
|
||||
|
Loading…
x
Reference in New Issue
Block a user