Skip to content

v0.29.0: keep undefined keys in dict & support custom object path in deserialization #195

v0.29.0: keep undefined keys in dict & support custom object path in deserialization

v0.29.0: keep undefined keys in dict & support custom object path in deserialization #195

Triggered via pull request November 23, 2024 04:09
Status Failure
Total duration 57s
Artifacts

dev.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 2 warnings
test (3.9, ubuntu-20.04)
Process completed with exit code 1.
test (3.10, ubuntu-20.04)
The job was canceled because "_3_9_ubuntu-20_04" failed.
test (3.13, ubuntu-20.04)
The job was canceled because "_3_9_ubuntu-20_04" failed.
test (3.13, ubuntu-20.04)
The operation was canceled.
test (3.12, ubuntu-20.04)
The job was canceled because "_3_9_ubuntu-20_04" failed.
test (3.12, ubuntu-20.04)
The operation was canceled.
test (3.11, ubuntu-20.04)
The job was canceled because "_3_9_ubuntu-20_04" failed.
test (3.11, ubuntu-20.04)
The operation was canceled.
test (3.9, ubuntu-20.04)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.9, ubuntu-20.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/