Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Collator build fails on the first run #174

Closed
JoshOrndorff opened this issue Aug 4, 2020 · 10 comments · Fixed by paritytech/substrate#7532
Closed

Collator build fails on the first run #174

JoshOrndorff opened this issue Aug 4, 2020 · 10 comments · Fixed by paritytech/substrate#7532

Comments

@JoshOrndorff
Copy link
Contributor

JoshOrndorff commented Aug 4, 2020

On the rococo_v1 tag (and probably on master) when I do a clean checkout and build the collator with cargo build --release -p rococo-collator, the command fails with the following (full error):

error: failed to run custom build command for `westend-runtime v0.8.22 (https://github.com/paritytech/polkadot?branch=rococo-branch#e9164236)`

Running the exact same command without changing anything succeeds the second time.

@bkchr
Copy link
Member

bkchr commented Aug 5, 2020

Hey, I need more output. I never had such a problem :)

@JoshOrndorff
Copy link
Contributor Author

@bkchr
Copy link
Member

bkchr commented Aug 6, 2020

Yeah that is a bug in the wasm-builder, which I still don't know on how to solve it..

@cecton
Copy link
Contributor

cecton commented Aug 6, 2020

I'm so used to it I don't even see it anymore

@JoshOrndorff
Copy link
Contributor Author

This issue is now preventing the docker image from building in the cumulus workshop. Is there a workaround? The best thing I can think of is to run cargo build --release three times in the Dockerfile. That's how I get around it locally.

@riusricardo
Copy link
Contributor

run cargo build --release three times in the Dockerfile

Is this a magic spell @JoshOrndorff ?

@bkchr
Copy link
Member

bkchr commented Sep 8, 2020

I really need to fix this. I already invested some thoughts and maybe just should get started and try my ideas.

@tolak
Copy link

tolak commented Oct 28, 2020

Did you sovled it? My VSCode always show me this error and it looks like makes the rust-analyzer extension stop working

@bkchr
Copy link
Member

bkchr commented Oct 28, 2020

Nope still exists.

@cecton
Copy link
Contributor

cecton commented Nov 25, 2020

Wow solved?! 🎉 GREAT!!!

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

Successfully merging a pull request may close this issue.

5 participants