Skip to content
tests

fix: Use either x509.not_valid_after_utc or if it does not exist, x509.not_valid_after #4974

Sign in to view logs

fix: Use either x509.not_valid_after_utc or if it does not exist, x509.not_valid_after

fix: Use either x509.not_valid_after_utc or if it does not exist, x509.not_valid_after #4974

Triggered via pull request June 24, 2025 19:42
@hessjcghessjcg
opened #1307
fix-x509-not-valid-after
Status Failure
Total duration 2m 14s
Artifacts –

tests.yml

on: pull_request
Matrix: integration tests
Matrix: unit tests
Fit to window
Zoom out
Zoom in

Annotations

17 errors
integration tests (ubuntu-latest, 3.9)
Process completed with exit code 1.
unit tests (3.13)
Process completed with exit code 1.
integration tests (macos-latest, 3.13)
Process completed with exit code 1.
integration tests (ubuntu-latest, 3.13)
Process completed with exit code 1.
unit tests (3.9)
Process completed with exit code 1.
integration tests (windows-latest, 3.13)
Process completed with exit code 1.
integration tests (macos-latest, 3.9)
Process completed with exit code 1.
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed
integration tests (windows-latest, 3.9)
Event loop is closed