Skip to content
Node.js CI

Partition based on samples instead of traceEvents when importing a sample-based chrome trace #245

Sign in to view logs

Partition based on samples instead of traceEvents when importing a sample-based chrome trace

Partition based on samples instead of traceEvents when importing a sample-based chrome trace #245

Triggered via pull request January 3, 2024 17:42
@zacharyfmarionzacharyfmarion
opened #460
zacharyfmarion:zac/use-samples
Status Success
Total duration 1m 23s
Artifacts –

ci.yml

on: pull_request
Matrix: test
finish
2s
finish
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
test (20.x)
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/
test (18.x)
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/