Skip to content

fix: display error details even if test has successful assertView results #660

fix: display error details even if test has successful assertView results

fix: display error details even if test has successful assertView results #660

Triggered via pull request October 23, 2023 23:29
Status Failure
Total duration 1m 25s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

node.js.yml

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

Annotations

7 errors and 4 warnings
build (18.x)
Process completed with exit code 1.
build (20.x)
Process completed with exit code 1.
build (16.x)
The operation was canceled.
build (14.x)
The operation was canceled.
build (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (14.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/