Conversation
|
Agreed, the error messages could go to a troubleshooting section. Not sure about the issues though, do you mean issues of other people who experienced the same? Anyway, I think those can be addressed in follow-ups and this particular PR improves the status quo which warrants merging as is. |
|
bot merge |
|
Waiting for commit status. |
| cargo build --release | ||
| ``` | ||
|
|
||
| Note that compilation can require several GiB of memory. Please make sure that the machine has that amount of physical memory or swap has enough capacity (keep in mind that if builds hit swap it tends to be very slow). |
There was a problem hiding this comment.
You should have said that more than 4GB are required :P
But people will not read this anyway and will continue to open issues xD
There was a problem hiding this comment.
Ah, 4GiB is also what I had in the back of my mind. I'll file another PR
But people will not read this anyway and will continue to open issues xD
Well, maybe, but at least those who reads this can save themselves a few back and forths
* master: Companion PR for #6984 (#1661) Update some dependencies. (#1718) Add a specific memory requirements (#1716) Companion PR for #7039: grandpa-rpc dont share subscription manager, only executor (#1687) Update bytes. (#1715) Add a note about memory requirements (#1714) Update parity-multiaddr. (#1700) typo in proxy tests (#1713) Companion PR for ` Add a `build-sync-spec` subcommand and remove the CHT roots from the light sync state.` (#1670) Forwardport: Validation: don't detect STDIN closing when running in process (#1695) (#1703)
Add a note about memory requirements for performing
cargo build --release