Flaky complement-crypto test

[richvdh]

This doesn't look specific to a particular test:

https://github.com/matrix-org/matrix-js-sdk/actions/runs/12158764040/job/33907406250

2024/12/04 11:28:35 Sharing [SERVER_NAME=hs1 SYNAPSE_COMPLEMENT_DATABASE=sqlite] host environment variables with container
  2024/12/04 11:28:43 Sharing [SERVER_NAME=hs2 SYNAPSE_COMPLEMENT_DATABASE=sqlite] host environment variables with container
  
  **********************************************************************************************
  Ryuk has been disabled for the current execution. This can cause unexpected behavior in your environment.
  More on this: https://golang.testcontainers.org/features/garbage_collector/
  **********************************************************************************************
  2024/12/04 11:28:49 github.com/testcontainers/testcontainers-go - Connected to docker: 
    Server Version: 26.1.3
    API Version: 1.45
    Operating System: Ubuntu 22.04.5 LTS
    Total Memory: 15981 MB
    Resolved Docker Host: unix:///var/run/docker.sock
    Resolved Docker Socket Path: /var/run/docker.sock
    Test SessionID: 0cb47af3517b8d4cb5424ae6b75c7d8ad589cd22dd7caae660434ae316010961
    Test ProcessID: 2817e95c-7044-4668-a7cc-bdff22a8f008
  2024/12/04 11:28:49 🐳 Creating container for image mitmproxy/mitmproxy:10.1.5
  2024/12/04 11:28:49 ✅ Container created: 908ec9f4f165
  2024/12/04 11:28:49 🐳 Starting container: 908ec9f4f165
  2024/12/04 11:28:50 ✅ Container started: 908ec9f4f165
  2024/12/04 11:28:50 🚧 Waiting for container id 908ec9f4f165 image: mitmproxy/mitmproxy:10.1.5. Waiting for: &{timeout:<nil> Log:loading complement crypto addons IsRegexp:false Occurrence:1 PollInterval:100ms}
  2024/12/04 11:28:53 🔔 Container is ready: 908ec9f4f165
      deploy.go:205: ComplementCryptoDeployment created (network=complement_crypto_dirty):
      deploy.go:206:   NAME          INT          EXT
      deploy.go:207:   synapse:      hs1          http://127.0.0.1:32769/ (rp=http://127.0.0.1:32777)
      deploy.go:208:   synapse:      hs2          http://127.0.0.1:32774/ (rp=http://127.0.0.1:32776)
      deploy.go:209:   mitmproxy:    mitmproxy    controller=http://127.0.0.1:32775/
      client.go:685: [CSAPI] POST hs1/_matrix/client/v3/register => 200 OK (24.633431ms)
      client.go:685: [CSAPI] POST hs1/_matrix/client/v3/register => 200 OK (16.125778ms)
      client.go:685: [CSAPI] POST hs1/_matrix/client/v3/createRoom => 200 OK (105.139932ms)
  JS SDK listening on http://127.0.0.1:44683/
      lang_jssdk.go:42: must.NotError: NewJSClient: %s -> failed to RunHeadless: failed to navigate to http://127.0.0.1:44683: websocket url timeout reached

[t3chguy]

Shouldn't this be filed against matrix-js-sdk or complement-crypto? Element Web doesn't run nor is involved in complement-crypto tests

[richvdh]

I thought we used this issue tracker to track test flakes that impeded work on this project.

Turns out it's not actually a flake, though.