Skip to content

Adding cancellation reason diagnostics #222

Adding cancellation reason diagnostics

Adding cancellation reason diagnostics #222

Triggered via pull request September 6, 2023 15:01
Status Failure
Total duration 41s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
test: test/e2e/ajax4/index.spec.ts#L20
Unsafe member access .didNetworkTimeOut on an `any` value
test: test/e2e/bfcache/index.spec.ts#L19
Unsafe member access .navigationType on an `any` value
test: test/e2e/bfcache/index.spec.ts#L30
Unsafe member access .navigationType on an `any` value
test: test/e2e/bfcache/index.spec.ts#L39
Unsafe member access .navigationType on an `any` value
test: test/e2e/images6/index.spec.ts#L24
Unsafe member access .didNetworkTimeOut on an `any` value
test: test/e2e/output1/index.spec.ts#L33
Unsafe member access .didNetworkTimeOut on an `any` value
test: test/e2e/output1/index.spec.ts#L35
Unsafe member access .lastVisibleChange on an `any` value
test: test/e2e/output2/index.spec.ts#L32
Unsafe member access .didNetworkTimeOut on an `any` value
test: test/e2e/output2/index.spec.ts#L35
Unsafe member access .lastVisibleChange on an `any` value
test: test/e2e/prerender1/index.spec.ts#L36
Unsafe member access .navigationType on an `any` value
test
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/