Fix fasttest by pinning pip dependencies

[azat]

After image update it prints the following warning:

/ClickHouse/tests/queries/0_stateless/01558_ttest_scipy.python:5: DeprecationWarning:
Pyarrow will become a required dependency of pandas in the next major release of pandas (pandas 3.0),
(to allow more performant data types, such as the Arrow string type, and better interoperability with other libraries)
but was not found to be installed on your system.
If this would cause problems for you,
please provide us feedback at https://github.com/pandas-dev/pandas/issues/54466

Pyarrow can be added as well, but according to the comment in the issue it bloats the image size 170%, so let's simply downgrade it for now and see how that issue will be resolved (or the warning could be suppressed of course).

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

[robot-clickhouse]

This is an automated comment for commit 92d96c4 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
ClickBench	Runs [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table	✅ success
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 server and keeper images	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
Docs check	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
Fast tests	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ 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
Mergeable Check	Checks if all other necessary checks are successful	✅ success
Push to Dockerhub	The check for building and pushing the CI related docker images to docker hub	✅ 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
Style check	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
Unit tests	Runs the unit tests for different release types	✅ success

Check name	Description	Status
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
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ error

[Algunenano]

I'm also looking in parallel into updating all of the dependencies (since newer Python requires newer deps) with:

RUN pip3 install numpy==1.26.3 scipy==1.12.0 pandas==2.2.0 pyarrow==15.0.0 Jinja2==3.1.3

Waiting on CI to see what works

[azat]

I'm also looking in parallel into updating all of the dependencies (since newer Python requires newer deps) with:

Great, I also though about pinning everything! Is the PR in some private repo? Or there is no PR yet?

[Algunenano]

Is the PR in some private repo?

Yes, but I'll bring it here if the CI is ok.

[azat]

pyarrow==15.0.0

As for adding pyarrow, it will increase image size to 100MB, and this is the thing that I was trying to avoid (maybe pandas will eventually remove requirement for pyarrow, since it seems that some people are unhappy)

[Algunenano]

You are right, I didn't check. Let's try pip install numpy==1.26.3 scipy==1.12.0 pandas==1.5.3 Jinja2==3.1.3 here if you don't mind

[azat]

Sure, I've adjusted the patch. And I've tested it locally image had been successfully built, let's see what CI will say.

[azat]

Fast test passed

[Felixoid]

@Algunenano, the backports are unnecessary, actually. Fast tests don't run for release branches anyhow