Skip to content
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

Merged
merged 10 commits into from
Apr 23, 2016
Merged

Conversation

nikomatsakis
Copy link
Contributor

@nikomatsakis nikomatsakis commented Apr 16, 2016

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

@nikomatsakis nikomatsakis force-pushed the compiletest-json branch 2 times, most recently from 8ed6452 to 492826c Compare April 16, 2016 10:26
@nikomatsakis
Copy link
Contributor Author

OK, I think make check is passing locally now. I encountered a bunch of niggling errors towards the end of the cycle.

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);
Copy link
Member

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?

Copy link
Contributor Author

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)
};

Copy link
Member

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 :)

@alexcrichton
Copy link
Member

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.

@nikomatsakis
Copy link
Contributor Author

@alexcrichton

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?

@alexcrichton
Copy link
Member

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 TMPDIR removed as that's probably papering over something which should be fixed elsewhere, but otherwise seems fine.

@nikomatsakis
Copy link
Contributor Author

@alexcrichton ok, I removed that TMPDIR change and I also tweaked the style a bit. :)

@nikomatsakis
Copy link
Contributor Author

@bors r=alexcrichton

@bors
Copy link
Contributor

bors commented Apr 18, 2016

📌 Commit aab0dd0 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Apr 18, 2016

⌛ Testing commit aab0dd0 with merge 090cf77...

@bors
Copy link
Contributor

bors commented Apr 18, 2016

💔 Test failed - auto-win-gnu-32-opt-rustbuild

@nikomatsakis
Copy link
Contributor Author

Linkcheck stage2 (i686-pc-windows-gnu)
panic_abort\fn.rust_eh_personality.html:50: broken link - src\panic_abort\lib.rs.html
panic_abort\fn.__rust_maybe_catch_panic.html:50: broken link - src\panic_abort\lib.rs.html
panic_abort\fn.__rust_start_panic.html:50: broken link - src\panic_abort\lib.rs.html
panic_abort\index.html:50: broken link - src\panic_abort\lib.rs.html
panic_unwind\fn.rust_eh_register_frames.html:50: broken link - src\panic_unwind\gcc\mod.rs.html
panic_unwind\fn.rust_eh_unregister_frames.html:50: broken link - src\panic_unwind\gcc\mod.rs.html
panic_unwind\fn.__rust_maybe_catch_panic.html:50: broken link - src\panic_unwind\lib.rs.html
panic_unwind\fn.__rust_start_panic.html:50: broken link - src\panic_unwind\lib.rs.html
panic_unwind\index.html:50: broken link - src\panic_unwind\lib.rs.html


command did not execute successfully: "C:\\bot\\slave\\auto-win-gnu-32-opt-rustbuild\\build\\obj\\build\\i686-pc-windows-gnu\\stage2-rustc\\i686-pc-windows-gnu\\release\\linkchecker.exe" "C:\\bot\\slave\\auto-win-gnu-32-opt-rustbuild\\build\\obj\\build\\i686-pc-windows-gnu\\doc"
expected success, got: exit code: 101


Makefile:40: recipe for target 'check' failed
Zombie process: "\Device\HarddiskVolume1\dojob.exe"
thread '<main>' panicked at 'found some broken links', C:\bot\slave\auto-win-gnu-32-opt-rustbuild\build\src\tools\linkchecker\main.rs:54
note: Run with `RUST_BACKTRACE=1` for a backtrace.
make: *** [check] Error 1

Hmm.

@nikomatsakis
Copy link
Contributor Author

@bors retry

@bors
Copy link
Contributor

bors commented Apr 18, 2016

⌛ Testing commit aab0dd0 with merge 4be56d7...

@bors
Copy link
Contributor

bors commented Apr 18, 2016

💔 Test failed - auto-win-gnu-32-opt-rustbuild

@alexcrichton
Copy link
Member

@bors: retry

On Mon, Apr 18, 2016 at 4:31 AM, bors [email protected] wrote:

[image: 💔] Test failed - auto-win-gnu-32-opt-rustbuild
http://buildbot.rust-lang.org/builders/auto-win-gnu-32-opt-rustbuild/builds/759


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#33020 (comment)

@bors
Copy link
Contributor

bors commented Apr 19, 2016

☔ The latest upstream changes (presumably #32755) made this pull request unmergeable. Please resolve the merge conflicts.

@nikomatsakis
Copy link
Contributor Author

@bors r=acrichto

@bors
Copy link
Contributor

bors commented Apr 19, 2016

📌 Commit 949a5ef has been approved by acrichto

@bors
Copy link
Contributor

bors commented Apr 21, 2016

⌛ Testing commit 399149a with merge a653136...

@bors
Copy link
Contributor

bors commented Apr 21, 2016

💔 Test failed - auto-win-msvc-64-opt-rustbuild

@nikomatsakis
Copy link
Contributor Author

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)
Copy link
Member

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.

@nikomatsakis
Copy link
Contributor Author

@bors r=acrichto

@bors
Copy link
Contributor

bors commented Apr 22, 2016

📌 Commit fd0632f has been approved by acrichto

@bors
Copy link
Contributor

bors commented Apr 22, 2016

⌛ Testing commit fd0632f with merge 0d6abb5...

@bors
Copy link
Contributor

bors commented Apr 22, 2016

💔 Test failed - auto-win-gnu-32-opt-rustbuild

@alexcrichton
Copy link
Member

@bors: retry

On Fri, Apr 22, 2016 at 3:41 AM, bors [email protected] wrote:

[image: 💔] Test failed - auto-win-gnu-32-opt-rustbuild
http://buildbot.rust-lang.org/builders/auto-win-gnu-32-opt-rustbuild/builds/804


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#33020 (comment)

@alexcrichton
Copy link
Member

@bors: r-

oh wait this one was legit

@sophiajt
Copy link
Contributor

@bors r=alexcrichton

@bors
Copy link
Contributor

bors commented Apr 22, 2016

📌 Commit 10d4cda has been approved by alexcrichton

Manishearth added a commit to Manishearth/rust that referenced this pull request Apr 22, 2016
…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
@bors
Copy link
Contributor

bors commented Apr 23, 2016

⌛ Testing commit 10d4cda with merge bb4b0d8...

bors added a commit that referenced this pull request Apr 23, 2016
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
@bors bors merged commit 10d4cda into rust-lang:master Apr 23, 2016
@nikomatsakis
Copy link
Contributor Author

nikomatsakis commented Apr 23, 2016

Huzzah! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants