Build fails on nightly (12ed235ad 2018-07-18) #236
Comments
On Mac OS artifact-frontend/target/deploy/docs/ was created, but not on RHEL7…
|
Thanks everyone. Traveling and moving for the next few days so will not get
to look at this for a bit
|
I have the same error (it seems so) and I think I might have found the reason. I poke around in I installed mdbook, and the error is gone when I re-run the build (I have also applied the Stacktrace:
Installed toolchains:
|
This fixed it for me too. So, to summarize:
|
Thanks for the detailed bug reports everyone! I've done what @zmitchell suggested, as well as add checks in This goes a long way. If anyone is interested in becoming a contributor to spearhead getting this building+releasing on multiple platforms I would be very interested! |
fixed in 2674c7c (hopefully) |
I've never done anything like that, but I'm willing to give it a go! |
Cool, if you've got the time and desire i could definitely use the help :)
- sent from my Android
…On Sun, Aug 5, 2018, 9:40 AM Zach Mitchell ***@***.***> wrote:
I've never done anything like that, but I'm willing to give it a go!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#236 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVCy--TO0VBsJ2o38rtxkgUp1PIFa-zks5uNyAGgaJpZM4VZtlv>
.
|
I'm on macOS 10.13.5, and I'm building
artifact
from source since there's no macOS binary (yet). Building from source gives me a number of errors, some of which I can fix.Edit: I should add that I'm using the source code from the release page.
Missing
cargo-web
dependencyThe first seems to be that
cargo-web
is required:I installed
cargo-web
separately viacargo install cargo-web
and things progressed.Bug in
stdweb < 0.4.8
This is a known issue (see here), and has already been fixed in
stdweb
. All I needed to do was updateCargo.toml
forartifact-frontend
.Incorrect paths used during build
I started running
cargo check
to speed things up, and I got this error message:As you can see, the panic is caused by unwrapping an error which is caused by a file/directory not being found. If you look at the backtrace, you'll see that the path
/Users/travis/...
is being used. I suspect that some CI stuff is leaking through to user installs, but I did verify that there's notravis
user on my computer usingdscl . list /Users | grep -v '^_'
. I'm not sure where thetravis
part is leaking through though.The text was updated successfully, but these errors were encountered: