wasm-bingen-test-runner is very slow for me, is there anything I can do to speed it up? #3237
-
When I execute tests marked with the I'm trying to unit test a component library I'm building for use in a I'm running this on WSL in Windows 11 with rustc 1.68.0-nightly, cargo 1.68.0-nightly, wasm-pack 0.10.3, Google Chrome 108.0.5359.124, & ChromeDriver 108.0.5359.71. FWIW The test also fails when it does finally run, even though the form element is created as expected when I run the leptos dev server, but that's likely an unrelated problem.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Y'all I finally figured this one out after coming back to it yesterday and digging around in headless chrome & chromedriver settings more. Looks like there's a known issue with chrome & gpu usage, so the {
"goog:chromeOptions": {
"args": [
"--disable-gpu"
]
}
}
|
Beta Was this translation helpful? Give feedback.
Y'all I finally figured this one out after coming back to it yesterday and digging around in headless chrome & chromedriver settings more. Looks like there's a known issue with chrome & gpu usage, so the
--disable-gpu
flag needs set in headless chrome to prevent errors that take forever to handle before moving on. For this case, I did it by setting the option inwebdriver.json
at my project root, like this: