Significant improvement of rust caching

[Felixoid]

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Follow-up for #52395. Cargo packages are now stored in S3 as a single archive per rust/Cargo.lock version. As well now rust is building with using of sccache.

[robot-clickhouse-ci-2]

This is an automated comment for commit dcb1d3e with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🔴 failure

Check name	Description	Status
AST fuzzer	Runs randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help	🟢 success
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	🟡 pending
ClickHouse build check	Builds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process	🟢 success
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	🟢 success
Docker image for servers	The check to build and optionally push the mentioned image to docker hub	🟢 success
Fast test	Normally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here	🟢 success
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	🟢 success
Install packages	Checks that the built packages are installable in a clear environment	🟢 success
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	🔴 failure
Mergeable Check	Checks if all other necessary checks are successful	🟢 success
Performance Comparison	Measure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests	🟢 success
Push to Dockerhub	The check for building and pushing the CI related docker images to docker hub	🟢 success
SQLancer	Fuzzing tests that detect logical bugs with SQLancer tool	🟢 success
Sqllogic	Run clickhouse on the sqllogic test set against sqlite and checks that all statements are passed	🟢 success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	🟢 success
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	🟢 success
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	🟢 success
Style Check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	🟢 success
Unit tests	Runs the unit tests for different release types	🟢 success
Upgrade check	Runs stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts	🔴 failure

[Felixoid]

Since there aren't objections, I am going to merge it after successful builds.

[Felixoid]

The plan here is to implement the same scheme as it was for ccache, details are here #53060 (comment)

[Felixoid]

The implemented solution is much simpler than the previous one.

The cargo cache is now stored in S3 in a single instance, and should be downloaded and uploaded much faster than previously.

[Felixoid]

The tests must finish, there are many changes in global things like S3 and de-/compressing

[Felixoid]

@azat I need assistant to backport it

As far as I get, I need to remove existing Cargo.lock in subdirs, add the config https://github.com/ClickHouse/ClickHouse/blob/master/rust/Cargo.toml, and edit it accordingly to the repository state. What's then? invoke cargo generate-lockfile in the rust/ directory?

[azat]

As far as I get, I need to remove existing Cargo.lock in subdirs, add the config master/rust/Cargo.toml, and edit it accordingly to the repository state. What's then? invoke cargo generate-lockfile in the rust/ directory?

More or less, but there are some trickiness, see below.

cd rust
cp /path/to/upstream/rust/Cargo.toml ./
rm */Cargo.lock
# then you need to pin versions in the */Cargo.toml strictly, i.e. not 'foo = "0.1"' but 'foo = "=0.1"'
# otherwise vendor make download different version and to decrease amount of changes
cargo generate-lockfile
cargo vendor # to check that it works
ninja -v cargo-build__ch_rust_blake3 cargo-build__ch_rust_skim_rust cargo-build__ch_rust_prql # this is required to ensure that vendored versions are correct, due to the tricky step with replacing versions in Cargo.toml
git checkout */Cargo.toml # revert this changes

Actually maybe the last command it extra and we need to pin the version, but let me take a look at it this separately, definitely it should not be a part of backports.

[Felixoid]

thanks, but it's indeed too much work to try to backport it