Skip to content

fix: merge ranges properly when contained by other ranges in set #257

fix: merge ranges properly when contained by other ranges in set

fix: merge ranges properly when contained by other ranges in set #257

Triggered via pull request November 2, 2023 22:21
Status Failure
Total duration 3m 40s
Artifacts

ci.yml

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

Annotations

32 errors and 5 warnings
test (14): packages/istanbul-lib-coverage/lib/file-coverage.js#L143
Replace `⏎················aItem,·aItemHits,·bMap,·bHits⏎············` with `aItem,·aItemHits,·bMap,·bHits`
test (14): packages/istanbul-lib-coverage/lib/file-coverage.js#L158
Replace `⏎············bItem,·bItemHits,·aMap,·aHits⏎········` with `bItem,·bItemHits,·aMap,·aHits`
test (14): packages/istanbul-lib-coverage/test/file.test.js#L1113
Replace `··········` with `············`
test (10)
The operation was canceled.
test (16): packages/istanbul-lib-coverage/lib/file-coverage.js#L143
Replace `⏎················aItem,·aItemHits,·bMap,·bHits⏎············` with `aItem,·aItemHits,·bMap,·bHits`
test (16): packages/istanbul-lib-coverage/lib/file-coverage.js#L158
Replace `⏎············bItem,·bItemHits,·aMap,·aHits⏎········` with `bItem,·bItemHits,·aMap,·aHits`
test (16): packages/istanbul-lib-coverage/test/file.test.js#L1113
Replace `··········` with `············`
test (12)
The operation was canceled.
windows: packages/istanbul-lib-coverage/lib/file-coverage.js#L143
Replace `⏎················aItem,·aItemHits,·bMap,·bHits⏎············` with `aItem,·aItemHits,·bMap,·bHits`
windows: packages/istanbul-lib-coverage/lib/file-coverage.js#L158
Replace `⏎············bItem,·bItemHits,·aMap,·aHits⏎········` with `bItem,·bItemHits,·aMap,·aHits`
windows: packages/istanbul-lib-coverage/test/file.test.js#L1113
Replace `··········` with `············`
test (14)
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 (10)
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 (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/
test (12)
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/
windows
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/