-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
port compiletest to use JSON output #33020
Conversation
8ed6452
to
492826c
Compare
OK, I think |
492826c
to
2a749a8
Compare
file_name: &str) { | ||
// We only consider messages pertaining to the current file. | ||
let matching_spans = | ||
|| diagnostic.spans.iter().filter(|span| span.file_name == file_name); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are some... interesting choices of indentation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you prefer this?
let matching_spans = || {
diagnostic.spans.iter().filter(|span| span.file_name == file_name)
};
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally, yeah, but I'm mostly just randomly commenting :)
Changes pretty much all look good to me, just a few minor nits here and there. I'm pretty scared about the style this is introducing but no need to block anything on that. |
Are you referring to the indentation, or something else? |
Yeah mostly how things are aligned to encourage rightward drift and how I have no idea how to configure an editor to automatically generate that style. That being said it's pretty minor. Oh and meant to say, r=me, the only real change I'd like to see is |
2a749a8
to
aab0dd0
Compare
@alexcrichton ok, I removed that TMPDIR change and I also tweaked the style a bit. :) |
@bors r=alexcrichton |
📌 Commit aab0dd0 has been approved by |
⌛ Testing commit aab0dd0 with merge 090cf77... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
Hmm. |
@bors retry |
⌛ Testing commit aab0dd0 with merge 4be56d7... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
@bors: retry On Mon, Apr 18, 2016 at 4:31 AM, bors [email protected] wrote:
|
☔ The latest upstream changes (presumably #32755) made this pull request unmergeable. Please resolve the merge conflicts. |
aab0dd0
to
949a5ef
Compare
@bors r=acrichto |
📌 Commit 949a5ef has been approved by |
⌛ Testing commit 399149a with merge a653136... |
💔 Test failed - auto-win-msvc-64-opt-rustbuild |
um. something is definitely messed up there... |
file_name: &str) { | ||
// We only consider messages pertaining to the current file. | ||
let matching_spans = || { | ||
diagnostic.spans.iter().filter(|span| span.file_name == file_name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think file_name
has backslashes normalized away, but span.file_name
does not, so on Windows this match never fires.
(discovered with @jonathandturner in person and he's working on a fix)
As a small note, using Path
here may help as that equality takes path normalization (like /
vs \
) into account.
@bors r=acrichto |
📌 Commit fd0632f has been approved by |
⌛ Testing commit fd0632f with merge 0d6abb5... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
@bors: retry On Fri, Apr 22, 2016 at 3:41 AM, bors [email protected] wrote:
|
@bors: r- oh wait this one was legit |
@bors r=alexcrichton |
📌 Commit 10d4cda has been approved by |
…excrichton port compiletest to use JSON output This uncovered a lot of bugs in compiletest and also some shortcomings of our existing JSON output. We had to add information to the JSON output, such as suggested text and macro backtraces. We also had to fix various bugs in the existing tests. Joint work with @jonathandturner. r? @alexcrichton
port compiletest to use JSON output This uncovered a lot of bugs in compiletest and also some shortcomings of our existing JSON output. We had to add information to the JSON output, such as suggested text and macro backtraces. We also had to fix various bugs in the existing tests. Joint work with @jonathandturner. r? @alexcrichton
Huzzah! :) |
This uncovered a lot of bugs in compiletest and also some shortcomings
of our existing JSON output. We had to add information to the JSON
output, such as suggested text and macro backtraces. We also had to fix
various bugs in the existing tests.
Joint work with @jonathandturner.
r? @alexcrichton