Added rusty db #1367
npmpublish.yml
on: pull_request
Matrix: test
publish-npm
0s
Annotations
15 errors
test/mysql/test.mysql.spec.ts > postgres test:
test/lib/test_lib.ts#L39
TypeError: Cannot read properties of undefined (reading 'toString')
❯ test/lib/test_lib.ts:39:32
|
test/mysql/test_mysql.spec.ts > /home/runner/work/ueberDB/ueberDB/test/mysql/test_mysql.spec.ts:
test/mysql/test_mysql.spec.ts#L81
TypeError: Cannot read properties of undefined (reading 'stop')
❯ test/mysql/test_mysql.spec.ts:81:21
|
test (mysql)
Process completed with exit code 1.
|
test (redis)
The job was canceled because "mysql" failed.
|
test (sqlite)
The job was canceled because "mysql" failed.
|
test (mongo)
The job was canceled because "mysql" failed.
|
test (mongo)
The operation was canceled.
|
test (redis)
The job was canceled because "mysql" failed.
|
test (couch)
The job was canceled because "mysql" failed.
|
test (couch)
The operation was canceled.
|
test (postgres)
The job was canceled because "mysql" failed.
|
Unhandled error:
lib/CacheAndBufferLayer.ts#L294
TypeError: Cannot read properties of null (reading 'close')
❯ Database.close lib/CacheAndBufferLayer.ts:294:26
❯ processTicksAndRejections node:internal/process/task_queues:95:5
This error originated in "test/postgres/test.postgresql.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "postgres test". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
test (postgres)
The operation was canceled.
|
test (elasticsearch)
The job was canceled because "mysql" failed.
|
test (elasticsearch)
The operation was canceled.
|