Skip to content
Node package

feature: improve a stack trace handling #1693

Sign in to view logs

feature: improve a stack trace handling

feature: improve a stack trace handling #1693

Triggered via push August 14, 2024 13:45
@gibiwgibiw
pushed afed832
feature/playwright
Status Failure
Total duration 26s
Artifacts –

npm.yml

on: push
Matrix: test
Matrix: build-n-publish
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
Project qase-newman - Node 16
Process completed with exit code 1.
Project qaseio - Node 16
The job was canceled because "_16_qase-newman" failed.
Project qaseio - Node 16
Process completed with exit code 1.
Project qase-javascript-commons - Node 16
The job was canceled because "_16_qase-newman" failed.
Project qase-javascript-commons - Node 16
The operation was canceled.
Project qase-cypress - Node 16
The job was canceled because "_16_qase-newman" failed.
Project qase-cypress - Node 16
Process completed with exit code 1.
Project qase-cucumberjs - Node 16
The job was canceled because "_16_qase-newman" failed.
Project qase-cucumberjs - Node 16
The operation was canceled.
Project qase-newman - Node 16
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Project qase-newman - Node 16
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/