Skip to content

fix: during the sharding upload process, a request id is thrown during abort #232

fix: during the sharding upload process, a request id is thrown during abort

fix: during the sharding upload process, a request id is thrown during abort #232

Re-run triggered July 18, 2023 03:19
Status Success
Total duration 6m 42s
Artifacts

master_node_test.yml

on: pull_request
Matrix: node_10
Matrix: browser_test
Matrix: node_12
Matrix: node_14
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
browser_test (14.x)
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/
node_10 (10.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/
node_12 (12.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/
node_14 (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/