diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-01-22 16:13:29 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-22 16:13:29 +0100 |
| commit | 9e896f42bd34ece60eec7c460bd9169cca98308a (patch) | |
| tree | a04142e7a7a1c335b8e5325acb605a6b9bd4ef14 /compiler/rustc_pattern_analysis/src | |
| parent | 34bab29ef9709bba4820de4e6df9cead013ae065 (diff) | |
| parent | 1afd216f760601fb13a9982d283ef8e2224b7527 (diff) | |
| download | rust-9e896f42bd34ece60eec7c460bd9169cca98308a.tar.gz rust-9e896f42bd34ece60eec7c460bd9169cca98308a.zip | |
Rollup merge of #119999 - onur-ozkan:remote-test-tools, r=Mark-Simulacrum
remote-test: use u64 to represent file size Currently, triggering a transfer of data exceeding the size of 4294967295 bytes results in a panic on the `remote-test-server` as `io::copy(&mut file, dst) failed with Connection reset by peer (os error 104)`. This issue happens because the size is transmitted as u32 to `remote-test-server`. First commit increases the supported file size. But I am not sure about its necessity — can we realistically encounter file sizes exceeding 4GB in builds, perhaps through some complicated configurations? ~The second commit adds a sanity check to avoid encountering the error `io::copy(&mut file, dst) failed with Connection reset by peer (os error 104)` on the `remote-test-server` side.~
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions