Xuanwo commented on issue #3809: URL: https://github.com/apache/incubator-opendal/issues/3809#issuecomment-1868268895
cc @Zheaoli, would you like to provide more context about your setup in https://github.com/apache/incubator-opendal/issues/3803#issuecomment-1868225255? I can't pass the `--chrome --headless` test for: ```shell Set timeout to 20 seconds... Running headless tests in Chrome on `http://127.0.0.1:34465/` Try find `webdriver.json` for configure browser's capabilities: Ok driver status: signal: 9 (SIGKILL) driver stdout: Starting ChromeDriver 114.0.5735.90 (386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}) on port 34465 Only local connections are allowed. Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe. ChromeDriver was started successfully. Error: http://127.0.0.1:34465/session/514ea4ed3b9ba5858d8327087d51795b/url: status code 404 error: test failed, to rerun pass `--lib` Caused by: process didn't exit successfully: `/home/xuanwo/.cargo/bin/wasm-bindgen-test-runner /home/xuanwo/Code/apache/incubator-opendal/target/wasm32-unknown-unknown/debug/deps/edge_test_s3_read_on_wasm-6c32d936916c1c6b.wasm` (exit status: 1) note: test exited abnormally; to see the full output pass --nocapture to the harness. Error: Running Wasm tests with wasm-bindgen-test failed Caused by: Running Wasm tests with wasm-bindgen-test failed Caused by: failed to execute `cargo test`: exited with exit status: 1 full command: cd "/home/xuanwo/Code/apache/incubator-opendal/core/edge/s3_read_on_wasm" && CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER="/home/xuanwo/.cargo/bin/wasm-bindgen-test-runner" CHROMEDRIVER="/home/xuanwo/.cache/.wasm-pack/chromedriver-365490088b2eefa3/chromedriver" WASM_BINDGEN_TEST_ONLY_WEB="1" "cargo" "test" "--target" "wasm32-unknown-unknown" ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
