Investigate chrome driver failure in wasm test

[th4s]

We should make sure that we understand what happened here:

https://github.com/tlsnotary/tlsn/actions/runs/10628828020/job/29464418444

[themighty1]

The actual error is a 404 for http://127.0.0.1:8013/favicon.ico
We may want to whitelist "favicon.ico" and not treat its absence as an error.

[heeckhau]

The 404 is not the reason the test fails; it fails because of a timeout.

local run:

2024-09-09T10:02:59.619976Z ERROR tlsn_wasm_test_runner::chrome_driver: LogEntry { source: Network, level: Error, text: "Failed to load resource: the server responded with a status of 404 (Not Found)", category: None, timestamp: Timestamp(1725876179619.673), url: Some("http://127.0.0.1:8013/favicon.ico"), line_number: None, stack_trace: None, network_request_id: Some(RequestId("89790.5")), worker_id: None, args: None }
test_notarize: passed
test_prove: passed
test_verifier: passed
3 passed, 0 failed

linked job output:

2024-08-30T07:51:06.504671Z  WARN run: chromiumoxide::browser: Browser was not closed manually, it will be killed automatically in the background
Error: Request timed out.
Error: Process completed with exit code 1.

[heeckhau]

@themighty1 This is still happening on alpha.7 from time to time: e.g.: https://github.com/tlsnotary/tlsn/actions/runs/11155476995/job/31006466036?pr=617

:48:21.975010Z  INFO start: tlsn_wasm_test_runner::wasm_server: listening on 127.0.0.1:8013
2024-10-03T03:48:21.975063Z  INFO start: tlsn_wasm_test_runner::ws: listening on: 127.0.0.1:8080
2024-10-03T03:48:21.975154Z  INFO start: tlsn_wasm_test_runner::server_fixture: listening on: 127.0.0.1:8083
2024-10-03T03:48:21.975450Z DEBUG run: tlsn_wasm_test_runner::chrome_driver: launching chromedriver
2024-10-03T03:48:26.546524Z DEBUG run: tungstenite::handshake::client: Client handshake done.    
2024-10-03T03:48:26.546[688](https://github.com/tlsnotary/tlsn/actions/runs/11155476995/job/31006466036?pr=617#step:8:689)Z DEBUG run: tlsn_wasm_test_runner::chrome_driver: chromedriver started
2024-10-03T03:50:26.546823Z  WARN run: chromiumoxide::browser: Browser was not closed manually, it will be killed automatically in the background
Error: Request timed out.
Error: Process completed with exit code 1.

BTW: Is this the same error as what went wrong with the browser benchmarks?

[themighty1]

@heeckhau , nope, i dont see any familiar errors. But this may indicate some wonkiness with chromiumoxide.

[themighty1]

@heeckhau Are you suggesting that this error still persists even after we added .incognito() ? https://github.com/tlsnotary/tlsn/blame/4d5102b6e141ecb84b8a835604be1d285ae6eaa5/crates/wasm-test-runner/src/chrome_driver.rs#L19

[heeckhau]

Yes, there must still be a race somewhere.
Sometimes the was tests still fail