Skip to content
basxconnect-ci

fix: error when users has unknown timezone #1807

Sign in to view logs

fix: error when users has unknown timezone

fix: error when users has unknown timezone #1807

Triggered via push February 12, 2025 06:34
@saemideluxesaemideluxe
pushed ee2e16d
main
Status Failure
Total duration 1m 8s
Artifacts –

main.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

16 errors
build (3.10, Django>=5.0)
Process completed with exit code 1.
build (3.11, Django>=5.0)
Process completed with exit code 1.
build (3.11, Django>=4.2)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.11, Django>=4.2)
Process completed with exit code 1.
build (3.13, Django>=4.2)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.13, Django>=4.2)
The operation was canceled.
build (3.12, Django>=5.0)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.12, Django>=5.0)
The operation was canceled.
build (3.10, Django>=4.2)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.10, Django>=4.2)
The operation was canceled.
build (3.9, Django>=4.2)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.9, Django>=4.2)
The operation was canceled.
build (3.12, Django>=4.2)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.12, Django>=4.2)
The operation was canceled.
build (3.13, Django>=5.0)
The job was canceled because "_3_10_Django__5_0" failed.
build (3.13, Django>=5.0)
The operation was canceled.