Uh oh!
There was an error while loading. Please reload this page.
fix stack overflow by enum and const - #36458
Conversation
rust-highfive
commented
Sep 13, 2016
r? @arielb1 (rust_highfive has picked a reviewer for you, use r? to override) |
bd5872e to
4972dd5Comparemikhail-m1
commented
Sep 14, 2016
I'll fix it |
ab3bb8a to
dc4a0cbComparebors
commented
Sep 22, 2016
☔ The latest upstream changes (presumably #36551) made this pull request unmergeable. Please resolve the merge conflicts. |
@arielb1 Could you look at my PR or may be suggest other reviewer? I'll fix conflicts ASAP |
arielb1
left a comment
There was a problem hiding this comment.
Your PR looks great, however:
- There are a few issues with the coding style. You should fix them.
- Your PR comment should mention the issue fixed - that some paths were skipped while checking for recursion.
There was a problem hiding this comment.
Why the 'b? Lifetime elision should insert it by itself.
There was a problem hiding this comment.
Why 2 lifetimes here? What was the problem with only 'a?
There was a problem hiding this comment.
Should be a NodeSet and not a Vec, to avoid O(n^2).
There was a problem hiding this comment.
nvm this is only non-empty when errors occur. Might want to add a comment to that effect?
There was a problem hiding this comment.
nit: function should be named process_def or something.
There was a problem hiding this comment.
nit: indentation. rustc style is to break after the equals sign. are you using rustfmt? Then don't. rustfmt sucks.
dc4a0cb to
d04e264Comparemikhail-m1
commented
Oct 4, 2016
@arielb1 Than you for review and sorry for long delay and rustfmt, I forgot run it after last fix. |
bors
commented
Oct 5, 2016
☔ The latest upstream changes (presumably #36814) made this pull request unmergeable. Please resolve the merge conflicts. |
… were skipped while checking for recursion.
d04e264 to
60891c9Comparearielb1
commented
Oct 5, 2016
@bors r+ |
bors
commented
Oct 5, 2016
📌 Commit 60891c9 has been approved by |
bors
commented
Oct 5, 2016
fix stack overflow by enum and const fixes#36163
bors
commented
Oct 5, 2016
💔 Test failed - auto-win-msvc-64-cargotest |
arielb1
commented
Oct 5, 2016
@bors retry |
bors
commented
Oct 5, 2016
alexcrichton
commented
Oct 5, 2016
@bors: retry force clean
|
bors
commented
Oct 5, 2016
⌛ Testing commit 60891c9 with merge 4a492ff... |
bors
commented
Oct 6, 2016
💔 Test failed - auto-win-msvc-64-cargotest |
alexcrichton
commented
Oct 6, 2016
@bors: retry On Wednesday, October 5, 2016, bors notifications@github.com wrote:
|
bors
commented
Oct 6, 2016
⌛ Testing commit 60891c9 with merge 5102bde... |
bors
commented
Oct 6, 2016
💔 Test failed - auto-win-msvc-64-cargotest |
alexcrichton
commented
Oct 6, 2016
@bors: retry On Wed, Oct 5, 2016 at 10:43 PM, bors notifications@github.com wrote:
|
alexcrichton
commented
Oct 6, 2016
@bors: r- er wait, this seems legitimate! |
mikhail-m1
commented
Oct 6, 2016
@alexcrichton How can I reproduce it locally? |
alexcrichton
commented
Oct 6, 2016
I believe this should work: ./configure --enable-rustbuild
make check-cargotest |
mikhail-m1
commented
Oct 7, 2016
@alexcrichton I rebuild it locally after pull and rebase and all tests passed successfully but on x86_64-unknown-linux-gnu |
mikhail-m1
commented
Oct 11, 2016
What should be my next step? |
alexcrichton
commented
Oct 11, 2016
How long did the build take? It looks like something is becoming perhaps pathologically slow although it may still complete (e.g. the build failed as it lacked output for awhile) |
@alexcrichton step with url crate (I think it's cargotest) took several seconds, may be some way to get some information from CI build? I can rebuild it again collect and share output. |
mikhail-m1
commented
Oct 14, 2016
testing https://github.com/iron/iron full log: https://www.dropbox.com/s/wbi7esu7a9mapxx/build2.log?dl=0 |
alexcrichton
commented
Oct 31, 2016
Closing due to inactivity but feel free to resubmit with tests fixed! |
fix stack overflow by enum and cont issue #36163 some paths were skipped while checking for recursion. I fixed bug reproduces on win64 cargo test. In previous PR #36458 time complexity was exponential in case of linked const values. Now it's linear. r? @alexcrichton
fixes#36163