S3 timeout logged now as debug not as an error · huridocs/uwazi@97388e1

Triggered via pull request September 19, 2024 09:42

daneryl

opened #7244

log_s3_timeout_as_debug

Status Success

Total duration 13m 14s

Artifacts 2

ci_unit_tests.yml

on: pull_request

4 warnings

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Produced during runtime

Name	Size
api-coverage-report Expired	68.3 KB
react-coverage-report Expired	58.7 KB