Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wasm-pack test --chrome --headless doesn't work for s3_read_on_wasm #3809

Closed
Tracked by #3803
Xuanwo opened this issue Dec 23, 2023 · 4 comments · Fixed by #3813
Closed
Tracked by #3803

wasm-pack test --chrome --headless doesn't work for s3_read_on_wasm #3809

Xuanwo opened this issue Dec 23, 2023 · 4 comments · Fixed by #3813

Comments

@Xuanwo
Copy link
Member

Xuanwo commented Dec 23, 2023

No description provided.

@Xuanwo
Copy link
Member Author

Xuanwo commented Dec 23, 2023

cc @Zheaoli, would you like to provide more context about your setup in #3803 (comment)?

I can't pass the --chrome --headless test for:

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"

@Zheaoli
Copy link
Member

Zheaoli commented Dec 23, 2023

Emmm, I don't have any extra setup

     Running unittests src/lib.rs (/home/manjusaka/Documents/projects/opendal/target/wasm32-unknown-unknown/debug/deps/edge_test_s3_read_on_wasm-5e605dcfcf0a6ce1.wasm)
Set timeout to 20 seconds...
Running headless tests in Chrome on `http://127.0.0.1:36985/`
Try find `webdriver.json` for configure browser's capabilities:
Ok
running 1 test                                    

test edge_test_s3_read_on_wasm::tests::test_hello_world ... ok

test result: ok. 1 passed; 0 failed; 0 ignored

@Zheaoli
Copy link
Member

Zheaoli commented Dec 23, 2023

Oh, I see, the chromedriver version need match the chrome version you are using

Google Chrome 120.0.6099.129 

╭─   manjusaka@manjusaka-garuda   ~/Documents/projects/opendal/core/edge/s3_read_on_wasm                                                                                                               main ⇣4 *2 !1   20:50:43  
╰─ chromedriver -v                       
ChromeDriver 120.0.6099.71 (9729082fe6174c0a371fc66501f5efc5d69d3d2b-refs/branch-heads/6099_56@{#13})

@Zheaoli
Copy link
Member

Zheaoli commented Dec 24, 2023

#3813

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants