solana 1.10.{3,5,6} build issue

[chenrui333]

👋 trying to build the latest release, but run into some build issue. The error log is as below:

build error

  error: cannot find derive macro `Deserialize` in this scope
    --> net-shaper/src/main.rs:12:10
     |
  12 | #[derive(Deserialize, Serialize, Debug)]
     |          ^^^^^^^^^^^
     |
  error: cannot find derive macro `Serialize` in this scope
    --> net-shaper/src/main.rs:12:23
     |
  12 | #[derive(Deserialize, Serialize, Debug)]
     |                       ^^^^^^^^^
     |
  error[E0277]: the trait bound `NetworkTopology: Deserialize<'_>` is not satisfied
      --> net-shaper/src/main.rs:375:9
       |
  375  |         serde_json::from_str(&config).expect("Failed to parse log as JSON");
       |         ^^^^^^^^^^^^^^^^^^^^ the trait `Deserialize<'_>` is not implemented for `NetworkTopology`
       |
  error[E0277]: the trait bound `NetworkTopology: Serialize` is not satisfied
      --> net-shaper/src/main.rs:482:42
       |
  482  |     let topology = serde_json::to_string(&config).expect("Failed to write as JSON");
       |                    --------------------- ^^^^^^^ the trait `Serialize` is not implemented for `NetworkTopology`
       |                    |
       |                    required by a bound introduced by this call
       |                 

full build log, https://github.com/Homebrew/homebrew-core/runs/5824825896
relates to

• solana 1.10.6 Homebrew/homebrew-core#98539
• solana 1.10.5 Homebrew/homebrew-core#98033
• solana 1.10.3 Homebrew/homebrew-core#97158

[l0k18]

I just want to weigh in that this error is exactly caused by running out of memory.

The cargo build command on a vanilla fresh clone of the repository needs at least 25gb of memory, and after necking down the parallelisation with a directive in .cargo/config.toml to 3, I was able to get it to pass through these things sooner, but then it got very stuck and chewed up 16gb on 3 parallel jobs, and one of them was a benchmark.

What is a benchmark doing in the middle of the build plan? This benchmark also hammered my spinning disk equipped (due to accident of a motherboard without an M.2 socket) machine even harder. I am pretty sure this benchmark has been delaying standard builds on most users machines by at least 15 if not 30 minutes from scratch.