Fix cache replay including extra newlines.#7819
Conversation
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
@bors: r+ |
|
📌 Commit 34ab15be23b16c4fc790c7eb0eb39762cdec7bd8 has been approved by |
|
⌛ Testing commit 34ab15be23b16c4fc790c7eb0eb39762cdec7bd8 with merge 8e75893dc66a46b9087666a780d3957e99404d7c... |
|
💔 Test failed - checks-azure |
|
@bors: retry hoping spurious timeout |
|
⌛ Testing commit 34ab15be23b16c4fc790c7eb0eb39762cdec7bd8 with merge befc8adcd1028154358446c3e3ff425dcbcadd32... |
|
💔 Test failed - checks-azure |
34ab15b to
7be3c2f
Compare
|
I pushed a fix that should fix the Windows error. I forgot that Windows treats PATH a little differently, and there was an infinite loop where the |
|
@bors: r+ |
|
📌 Commit 7be3c2f has been approved by |
Fix cache replay including extra newlines. The compiler output cache replay was changed in #7737 to use `BufReader::read_line` instead of `str::lines`. `read_line`, unlike `lines`, includes the trailing line ending. The code is written assuming that the line endings are stripped, so make sure they are stripped here, too. This only happens for non-JSON messages, like `RUSTC_LOG`.
|
☀️ Test successful - checks-azure |
The compiler output cache replay was changed in #7737 to use
BufReader::read_lineinstead ofstr::lines.read_line, unlikelines, includes the trailing line ending. The code is written assuming that the line endings are stripped, so make sure they are stripped here, too.This only happens for non-JSON messages, like
RUSTC_LOG.