Skip to content

Reformat log statements so that they aren't susceptible to formatting errors and worse when {} are in the message #2653

Reformat log statements so that they aren't susceptible to formatting errors and worse when {} are in the message

Reformat log statements so that they aren't susceptible to formatting errors and worse when {} are in the message #2653

Triggered via pull request October 19, 2024 02:00
Status Failure
Total duration 2m 20s
Artifacts

CI.yml

on: pull_request
Matrix: python-tests
style-check
46s
style-check
python-lint
6s
python-lint
gradle-tests
37s
gradle-tests
python-e2e-tests
1m 58s
python-e2e-tests
cdk-tests
30s
cdk-tests
link-checker
4s
link-checker
console-api-tests
35s
console-api-tests
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
cdk-tests
Process completed with exit code 1.
gradle-tests
Process completed with exit code 1.
style-check
Process completed with exit code 1.
python-e2e-tests
Process completed with exit code 1.
python-e2e-tests
Process completed with exit code 1.
all-ci-checks-pass
Process completed with exit code 1.
gradle-tests
No files were found with the provided path: **/build/reports/tests/ **/reports/jacoco/mergedReport/. No artifacts will be uploaded.
python-e2e-tests
No files were found with the provided path: logs/docker logs/opensearch_benchmark_logs logs/shared_logs_output. No artifacts will be uploaded.