Skip to content

chore: Adding stack trace for errors in fetching tenant from redis to debug the root cause #22543

chore: Adding stack trace for errors in fetching tenant from redis to debug the root cause

chore: Adding stack trace for errors in fetching tenant from redis to debug the root cause #22543

Triggered via pull request January 24, 2025 15:46
Status Failure
Total duration 25m 45s
Artifacts 1

quality-checks.yml

on: pull_request
path-filter
10s
path-filter
server-spotless  /  spotless-check
2m 9s
server-spotless / spotless-check
server-unit-tests  /  server-unit-tests
25m 10s
server-unit-tests / server-unit-tests
client-build  /  client-build
client-build / client-build
client-check-cyclic-deps  /  check-cyclic-dependencies
client-check-cyclic-deps / check-cyclic-dependencies
client-lint  /  client-lint
client-lint / client-lint
client-prettier  /  prettier-check
client-prettier / prettier-check
client-unit-tests  /  client-unit-tests
client-unit-tests / client-unit-tests
qc-result
0s
qc-result
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
server-unit-tests / server-unit-tests
Process completed with exit code 1.
qc-result
Process completed with exit code 1.
path-filter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
server-spotless / spotless-check
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
qc-result
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
failed-server-tests
250 Bytes