Skip to content

Changing from aws-chromelambda to @sparticuz/chromium #388

Changing from aws-chromelambda to @sparticuz/chromium

Changing from aws-chromelambda to @sparticuz/chromium #388

Status Success
Total duration 2m 39s
Artifacts 1

tests.yml

on: pull_request
Unit tests
4m 37s
Unit tests
Static analysis
1m 55s
Static analysis
Integration tests: CLI
4m 12s
Integration tests: CLI
Visual tests: React DOM
2m 28s
Visual tests: React DOM
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Static analysis
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/
Integration tests: CLI
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/
Unit tests
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/
Visual tests: React DOM
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/

Artifacts

Produced during runtime
Name Size
react-example-screenshots Expired
852 KB