Skip to content

Recognize typical assertion errors and use their formatting #1285

Recognize typical assertion errors and use their formatting

Recognize typical assertion errors and use their formatting #1285

Triggered via pull request April 12, 2023 10:51
Status Failure
Total duration 5m 33s
Artifacts

ci.yml

on: pull_request
Test package-lock for unexpected modifications
35s
Test package-lock for unexpected modifications
Install dependencies without using a lockfile
2m 31s
Install dependencies without using a lockfile
Lint source files
49s
Lint source files
Matrix: Node.js
Matrix: TypeScript compatibility
Fit to window
Zoom out
Zoom in

Annotations

11 errors
Lint source files: test/external-assertions/fixtures/assert-failure.js#L1
There should be at least one empty line between import groups
Lint source files: test/external-assertions/fixtures/assert-failure.js#L2
`node:assert` import should occur before import of `ava`
Lint source files: test/external-assertions/test.js#L1
There should be at least one empty line between import groups
Lint source files
Process completed with exit code 1.
Node.js (^18, ubuntu-latest)
Process completed with exit code 1.
Node.js (^16.15, ubuntu-latest)
Process completed with exit code 1.
Node.js (^14.19, ubuntu-latest)
Process completed with exit code 1.
Install dependencies without using a lockfile
Process completed with exit code 1.
Node.js (^14.19, windows-latest)
Process completed with exit code 1.
Node.js (^16.15, windows-latest)
Process completed with exit code 1.
Node.js (^18, windows-latest)
Process completed with exit code 1.