I suspect we finally hit the memory limit. When building locally, rustc memory usage spikes up to over 4GiB so this seems very likely...
What should we do? I have a few ideas:
Only build docs with a select number of chips enabled. I guess we could just choose the most used AVR microcontrollers and only provide online docs for those. For other chips people can build documentation locally using
cargo doc --features atmega328p --open
Find out why memory usage is so high? I'm not sure if there is anything we can do about it short of changing the codegen in svd2rust...
Ask the docs.rs team to increase the limits. Honestly, I am not a fan of this because the solution doesn't scale when more chips get added in the future...
See https://docs.rs/crate/avr-device/0.3.3/builds/556355.
I suspect we finally hit the memory limit. When building locally, rustc memory usage spikes up to over 4GiB so this seems very likely...
What should we do? I have a few ideas:
svd2rust
...