`cargo raze` fails on macOS if `/tmp/cargo-raze/doesnt/exist` doesn't exist about cargo-raze

[groszewn]

Note, we avoid this error in the meantime by specifying --locked during cargo install to ensure the Cargo.lock is honored (instead of having transitive dependencies upgraded).

[yatbear]

I got this error in Linux as well. Additionally this failure has been occurring in one of the CI jobs in my local fork: https://github.com/yatbear/tensorboard/actions/runs/4491201369/jobs/7899333584, but weirdly not in the upstream CI.

[yatbear]

Hi cargo-raze team,

This error is now occurring in our main repo now: https://github.com/tensorflow/tensorboard/actions/runs/4574349463/jobs/8078646809

Could you please provide some pointers for this? Thanks!

[groszewn]

This seems to be coming from Keats/tera#819, as far as I can tell.

[dayfine]

I saw this when running on Circle CI too, I had to add a line to mkdir -p /tmp/cargo-raze/doesnt/exist/

[dayfine]

Probably just need to first create the path instead of relying on certain behavior at Tera's level?