Uh oh!
There was an error while loading. Please reload this page.
Add a regression test for #29122 (fixed in #29134) - #29151
Conversation
rust-highfive
commented
Oct 18, 2015
(rust_highfive has picked a reviewer for you, use r? to override) |
pnkfelix
commented
Oct 18, 2015
@bors r+ rollup |
bors
commented
Oct 18, 2015
📌 Commit 19041cd has been approved by |
I suspect this won't work on Windows, but let's be optimistic and try it before disabling.
steveklabnik
commented
Oct 19, 2015
@bors: r- this caused rollup failure |
wthrowe
commented
Oct 20, 2015
I've fixed the pretty failures and I think the test should be working on OS X now. |
alexcrichton
commented
Oct 20, 2015
…ichton I suspect this won't work on Windows, but let's be optimistic and try it before disabling.
steveklabnik
commented
Oct 20, 2015
wthrowe
commented
Oct 20, 2015
I do not understand this new error. There is rustc output indicating a successful compilation of a staticlib, but then the expected staticlib does not exist. |
There was a problem hiding this comment.
The STATICLIB macro here is expanding to library.lib on Windows when a staticlib output always produces libfoo.a (e.g. liblibrary.a in this case)
There was a problem hiding this comment.
The reference could use an update, then. (I'm not going to do it because, as shown here, I don't understand what's going on well enough to write something useful.)
I think at this point I'm just going to disable the test on Windows, if no one objects. I expect that the linking command won't work there anyway, and it seems like there might be several more cycles of this before I even figure out how to attempt to link a Windows native library. Someone who can do local testing and actually knows how to develop for Windows can fix it if they want to.
There was a problem hiding this comment.
Oh weird! Yeah that documentation should probably be updated!
Could this just hardcode liblibrary.a for now to work on Windows as well? In general we prefer to have tests run everywhere whenever possible.
wthrowe
commented
Oct 21, 2015
Modified to be a no-op on Windows. |
b41963e to
e6626a8Comparewthrowe
commented
Oct 21, 2015
(Moving to the main comment thread from line comments.) Alright, try this version. I should probably point out that if this does work on Windows and actually tests what it's supposed to then it would seem I've created a file whose name can't be stored in a |
alexcrichton
commented
Oct 21, 2015
Thanks! Could you also squash this down to one commit? |
19664fd to
0dce92aComparewthrowe
commented
Oct 22, 2015
Squashed. |
alexcrichton
commented
Oct 22, 2015
…ichton I suspect this won't work on Windows, but let's be optimistic and try it before disabling.
bors
commented
Oct 22, 2015
I suspect this won't work on Windows, but let's be optimistic and try it before disabling.
alexcrichton
commented
Oct 22, 2015
@bors: r- I think this caused a legitimate failure |
alexcrichton
commented
Oct 22, 2015
@bors: force |
bors
commented
Oct 22, 2015
⛄ The build was interrupted to prioritize another pull request. |
steveklabnik
commented
Oct 22, 2015
I wasn't sure |
steveklabnik
commented
Oct 22, 2015
Can we not roll this up in the future? It's already caused three rollups to fail. |
steveklabnik
commented
Oct 22, 2015
@bors: rollup- |
wthrowe
commented
Oct 22, 2015
Not much to go on. The failed command is a grep, so in failing it swallowed all the debugging output. |
alexcrichton
commented
Oct 22, 2015
This may actually be a bug in MinGW's If that's the case where this just unfortunately doesn't work on Windows then could you add a comment as such before ignoring it? |
0dce92a to
a1c8431Comparewthrowe
commented
Oct 24, 2015
This look good? |
alexcrichton
commented
Oct 24, 2015
I suspect this won't work on Windows, but let's be optimistic and try it before disabling.
I suspect this won't work on Windows, but let's be optimistic and try it before disabling.