Skip to content

update problematic tls keyword #111

update problematic tls keyword

update problematic tls keyword #111

Re-run triggered November 18, 2024 17:09
Status Failure
Total duration 20s
Artifacts

development.yaml

on: pull_request
Matrix: test
publish-docs
0s
publish-docs
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
test (R2019a, 5.7)
Process completed with exit code 127.
test (R2019a, 8.0.18)
Process completed with exit code 127.
test (R2019a, 5.6)
The job was canceled because "R2019a_5_7" failed.
test (R2019a, 5.6)
Process completed with exit code 127.
test (R2019a, 5.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 (R2019a, 5.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (R2019a, 8.0.18)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 (R2019a, 8.0.18)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/