Uh oh!
There was an error while loading. Please reload this page.
Fix how paths are printed by error messages during bootstrap - #47731
Fix how paths are printed by error messages during bootstrap#47731wesleywiser wants to merge 2 commits into
Conversation
rust-highfive
commented
Jan 25, 2018
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
pnkfelix
commented
Jan 25, 2018
Looks to me like this is exactly what @alexcrichton called for in this comment; great! Thanks! |
pnkfelix
commented
Jan 25, 2018
@bors r+ |
bors
commented
Jan 25, 2018
📌 Commit 4005430 has been approved by |
bors
commented
Jan 25, 2018
☔ The latest upstream changes (presumably #47740) made this pull request unmergeable. Please resolve the merge conflicts. |
4005430 to
c6faac4Comparewesleywiser
commented
Jan 25, 2018
Rebased. |
alexcrichton
commented
Jan 25, 2018
@bors: r=pnkfelix |
bors
commented
Jan 25, 2018
📌 Commit c6faac4 has been approved by |
ollie27
commented
Jan 25, 2018
bors
commented
Jan 26, 2018
☔ The latest upstream changes (presumably #47676) made this pull request unmergeable. Please resolve the merge conflicts. |
shepmaster
commented
Feb 3, 2018
Ping from triage, @wesleywiser! You have merge conflicts that need to be addressed! |
BatmanAoD
commented
Feb 7, 2018
@wesleywiser Ping from triage; just wanted to let you know that in two days this PR will be closed for inactivity, unless you respond to the request to resolve merge conflicts. Note that this isn't necessarily a dead end; you will of course be free to reopen once you've resolved the conflicts. |
wesleywiser
commented
Feb 7, 2018
Thanks @shepmaster and @BatmanAoD! I'm getting back from some vacation time and still trying to dig through my inbox. I'll have some time tomorrow night to fix this up. |
65d6cf0 to
0eb5283Comparebors
commented
Feb 11, 2018
☔ The latest upstream changes (presumably #47657) made this pull request unmergeable. Please resolve the merge conflicts. |
0eb5283 to
7581336Comparewesleywiser
commented
Feb 13, 2018
Fixed. |
alexcrichton
commented
Feb 13, 2018
@bors: r+ |
bors
commented
Feb 13, 2018
📌 Commit 7581336 has been approved by |
bors
commented
Feb 15, 2018
☔ The latest upstream changes (presumably #48202) made this pull request unmergeable. Please resolve the merge conflicts. |
bors
commented
Feb 24, 2018
⌛ Testing commit 65b0f834cd538a3da551d3355bb134a843c36f37 with merge 0bed0be4d9e06b9eea856120dac66ce2f1a30191... |
bors
commented
Feb 24, 2018
☔ The latest upstream changes (presumably #48476) made this pull request unmergeable. Please resolve the merge conflicts. |
bors
commented
Feb 24, 2018
💔 Test failed - status-travis |
kennytm
commented
Feb 24, 2018
Cannot build bootstrap in Details |
65b0f83 to
2a6035dCompareMark-Simulacrum
commented
Feb 24, 2018
Fixed and rebased. @bors r+ p=1 |
bors
commented
Feb 24, 2018
📌 Commit 2a6035d has been approved by |
bors
commented
Feb 24, 2018
⌛ Testing commit 2a6035d3772fb635b2ab73dc24319ddcca029bbb with merge fb3ec5c0902a49bf6744fd8e138fa278a5b0bb4e... |
bors
commented
Feb 24, 2018
💔 Test failed - status-travis |
2a6035d to
ebebe63CompareMark-Simulacrum
commented
Feb 24, 2018
I'm starting to become frustrated with this -- it looks like every piece of infra doesn't want us to do this. @alexcrichton Is there a chance you have an easy way to avoid the above error? Maybe we can tell Cargo that the "root" toml file doesn't actually matter for our build directory (note that hard coding this isn't really a good idea since relative build paths are relatively typical AIUI). |
alexcrichton
commented
Feb 24, 2018
Unfortunately I don't think so, there's no way currently to tell Cargo "no please don't look up past this directory for a workspace root" |
Fixes#47355