search

tlsnotary / tlsn

Rust implementation of the TLSNotary protocol
https://tlsnotary.org
261 stars 70 forks source link

Investigate chrome driver failure in wasm test #576

Open th4s opened 2 weeks ago

th4s commented 2 weeks ago

We should make sure that we understand what happened here:

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

themighty1 commented 1 week ago

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 commented 1 week ago

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.