)]}'
{
  "commit": "d7a36c133befa0e898817af73363a3e74975bcfe",
  "tree": "772c914675b43531ebfae31d16ce63da3faf0f8e",
  "parents": [
    "d645a4c9c563b80048ce5f32845e754a67f11efa",
    "6bd5de70eece499ba157e38f23685dce09e5689f"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "476013+matthiaskrgr@users.noreply.github.com",
    "time": "Fri Nov 28 15:19:15 2025 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Nov 28 15:19:15 2025 +0100"
  },
  "message": "Rollup merge of #147952 - ferrocene:pvdrz/remote-test-client-timeout, r\u003dEnselic\n\nAdd a timeout to the `remote-test-client` connection\n\nCurrently, the `remote-test-client` doesn\u0027t have a timeout when connecting to the `remote-test-server`. This means that running tests using it can hang indefinitely which causes issues when running tests on CI, for example.\n\nThis PR now sets a default timeout of 5 minutes, meaning that if, for example, `TEST_DEVICE_ADDR\u003d\u003cIP:PORT\u003e ./x test --target riscv64gc-unknown-linux-gnu tests/ui` is run and the `remote-test-server` is not reachable by the client, the client will panic after the timeout is reached.\n\nAdditionally, the `TEST_DEVICE_CONNECT_TIMEOUT` env variable can be used to set up the timeout to any value (in seconds).\n\nThis PR also wires up a test step for `remote-test-client`, which didn\u0027t previously have tool tests run in CI.\n\nEdit: ~~blocked by rust-lang/rust#149071~~\n",
  "tree_diff": []
}