Bump the python-packages group with 2 updates #1829
pre-commit-ci[bot]tests.yml
on: pull_request
Oracle tests
/
Run Oracle tests
7m 26s
Clickhouse tests
/
Run Clickhouse tests
8m 53s
MySQL tests
/
Run MySQL tests
7m 7s
MSSQL tests
/
Run MSSQL tests
7m 24s
HDFS tests
/
Run HDFS tests
11m 3s
Hive tests
/
Run Hive tests
7m 11s
Iceberg tests
/
Run Iceberg tests
7m 17s
S3 tests
/
Run S3 tests
10m 51s
SFTP tests
/
Run SFTP tests
6m 25s
FTP tests
/
Run FTP tests
8m 48s
FTPS tests
/
Run FTPS tests
6m 3s
Samba tests
/
Run Samba tests
6m 18s
WebDAV tests
/
Run WebDAV tests
6m 23s
Scheduler tests
/
Run Scheduler tests
4m 38s
Unit tests
/
Run unit tests
2m 36s
Tests done
16s
Annotations
1 error and 15 warnings
|
HDFS tests / Run HDFS tests
Process completed with exit code 1.
|
|
Unit tests / Run unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Scheduler tests / Run Scheduler tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FTPS tests / Run FTPS tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Samba tests / Run Samba tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
SFTP tests / Run SFTP tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
WebDAV tests / Run WebDAV tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MySQL tests / Run MySQL tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Hive tests / Run Hive tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Iceberg tests / Run Iceberg tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
MSSQL tests / Run MSSQL tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Oracle tests / Run Oracle tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Clickhouse tests / Run Clickhouse tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FTP tests / Run FTP tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
S3 tests / Run S3 tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
HDFS tests / Run HDFS tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, jwalton/gh-docker-logs@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
MTSWebServices~syncmaster~7AULJW.dockerbuild
|
70.2 KB |
sha256:2038e4caccdc28599bf45bcf8d87029e7acaea252213c0364704663086ab2c68
|
|
|
MTSWebServices~syncmaster~E86EYR.dockerbuild
|
70.9 KB |
sha256:e7d4776287d8b50910935b444b832b25c2a84449939a9bed8eb6cff9148ac38e
|
|
|
MTSWebServices~syncmaster~J7FKHF.dockerbuild
|
71.1 KB |
sha256:b5d6d566623f20eab4f757bcfed14725bac981ccce67eb884d8e54d96eb89a4e
|
|
|
MTSWebServices~syncmaster~N3RML7.dockerbuild
|
70.5 KB |
sha256:d5d09d3b26a2b0571b5e031d1931300ce539f18fc9ff73b487b5151ffb9026ae
|
|
|
MTSWebServices~syncmaster~N57OFF.dockerbuild
|
70.6 KB |
sha256:8b791684bd345e63b127cbb394d81caf7cb716fe8f81b3c3e8e215c99e3140fa
|
|
|
MTSWebServices~syncmaster~N5BVAY.dockerbuild
|
71 KB |
sha256:9379d45f39382505e3233ae959edd15dd28375ea30519d4ab00cc08b757aba75
|
|
|
MTSWebServices~syncmaster~RCOA4G.dockerbuild
|
79 KB |
sha256:befec8d7dd9a7d2c7a2c8d31e290f1b6338ea983a2d3c002ec40b6c0b7a6e1f4
|
|
|
MTSWebServices~syncmaster~SGII3I.dockerbuild
|
69.9 KB |
sha256:bba3849f4048b839c38a53385a0e055d4024923589855569e3d9e363cf5cd5fa
|
|
|
MTSWebServices~syncmaster~SP8NYQ.dockerbuild
|
70.8 KB |
sha256:4fa3308d9aa86c7b23b6969d47acba561a16739c26015649ee907763b5f436b7
|
|
|
MTSWebServices~syncmaster~TKAIA7.dockerbuild
|
69.5 KB |
sha256:1c8bccee8050ca06bbb64d1d7f8b3449c11a5c585b0882e65f772ec73cc6f8cd
|
|
|
MTSWebServices~syncmaster~TX2D9P.dockerbuild
|
70.7 KB |
sha256:fe0413ea17a823b388187250f9bd8c3663d541c468422168912c39b3036d55f8
|
|
|
MTSWebServices~syncmaster~VDVEYM.dockerbuild
|
70.1 KB |
sha256:6ee1cafe8c3b8dcd3b6a2693a5759337ba44da43c63eb572364166ea93a50253
|
|
|
MTSWebServices~syncmaster~VZ2LR0.dockerbuild
|
70.6 KB |
sha256:1205a4028eaee603f863e8156ca3561612c1d53e32b4876888892a419faa9110
|
|
|
MTSWebServices~syncmaster~Y44CYM.dockerbuild
|
70.9 KB |
sha256:4cc1a5e63e76a5e057076b4e1c67df58536428102455bbcda043dd47bfc8a19a
|
|
|
coverage-clickhouse
|
324 KB |
sha256:70bc94ec228501154944f695a74cb97ab46365ba05755c65287ef389e8601647
|
|
|
coverage-ftp
|
412 KB |
sha256:0f92ac16d6f1acd8865470638968e02a0e1217f282616c87b8862422a14bb3a1
|
|
|
coverage-ftps
|
240 KB |
sha256:6f5a50e50ccd8f5c95066fd94f72e28249fc5a2867d83672f953f99ee6d51a45
|
|
|
coverage-hdfs
|
371 KB |
sha256:6f4c51c331ffecfa8500478a5e65e62d791dd1e2c1023985a645d3a1dc472d3b
|
|
|
coverage-hive
|
273 KB |
sha256:0400a370458cb40295e092e6e098a0f1c234827ed86abc68e8d25c3ebd78cc1a
|
|
|
coverage-iceberg
|
278 KB |
sha256:8946d179a85df57d93a56104ec944e9b642da734ce548688d7caf30f49fc0007
|
|
|
coverage-mssql
|
273 KB |
sha256:0788b6487702a731af66d32226942f02246157db52d2f5b49c5a760a8b143302
|
|
|
coverage-mysql
|
272 KB |
sha256:f1a0e1b7acac52d8658ca2161c41e912f171af976ab1abbaf4c7cda2d6230d6e
|
|
|
coverage-oracle
|
273 KB |
sha256:637d5b9977d61f8e60c39da2dbb77e610baf7e97051b8365a0a5739abb8c6de7
|
|
|
coverage-s3
|
297 KB |
sha256:36e83588b1ccda6026f9932c26e89ab5ce5bed3ac8925c303320566b4ac80b06
|
|
|
coverage-samba
|
240 KB |
sha256:12e51b9fb1107bf48069ce9074aeb02f04ce639b77245fb08a6cc98998a7b333
|
|
|
coverage-scheduler
|
194 KB |
sha256:99dabddb3a4532e4e70769fda63a36697658166a191b5e511f01badbe49b3238
|
|
|
coverage-sftp
|
241 KB |
sha256:8ccf694487dc0477e447fe933ac30d97c086504f7be3fd655b9da257f0b35285
|
|
|
coverage-unit
|
131 KB |
sha256:70bc9b9a350a37479225198d52994f3ffbe539b0e06b0a72e647931ba576dcc3
|
|
|
coverage-webdav
|
239 KB |
sha256:45dd94dcd4c4b4cd56184994ce21a9dece768b0ba8229582c347b977a9de5240
|
|
|
worker-logs-hdfs
|
141 KB |
sha256:4c4f755a7fb29a7bc07ad747bf8a152a12bc4f6cd1d3a815e4408282c9be95f5
|
|