glibc errors in ci

[tessus]

@orhun there are more and more glibc errors in the CI. maybe it has something to do with the ubuntu-latest label, but in the rustypaste repo we also see lychee glibc errors with ubuntu-22.04 (although the lychee action might use its own OS).

So I am not entirely sure what is going on, especially since some errors are intermittent.

[orhun]

We should probably pin the version of the runners and Rust toolchain. Otherwise things will keep breaking spuriously.

[tessus]

Not a bad idea, but we have to find the right combination, otherwise the lints and clippy might be a problem. e.g. when we use the latest version locally and run cargo fmt it might change it to something that a previous version (in the CI workflow) sees differently and thus the CI will fail.

We might have to set a rust toolchain in the Cargo.toml...

Any ideas?

[orhun]

I think rust-toolchain.toml is the best option here.

We could also do less aggressive testing in the CI - remove a bunch of targets and only focus on the ones that are important. No nightly or beta toolchain as well.

Probably a good idea to do before #264

Wdyt?

[tessus]

sounds good. I'll look into it tomorrow. I'm beat today.

[tessus]

so, it's actually the other way around. ubuntu-22.04 has a pretty old glibc, so -latest should actually be the better option, since most action use newer images.

I've still added a rust-toolchain.yml, which only specifies stable.