Skip to content
JS SDK

Enable MLS in Docker container, run MLS client tests in CI #85

Sign in to view logs

Enable MLS in Docker container, run MLS client tests in CI

Enable MLS in Docker container, run MLS client tests in CI #85

Triggered via pull request September 16, 2024 17:10
@ryginerygine
synchronize #664
rygine/update-ci
Status Failure
Total duration 1m 58s
Artifacts –

js-sdk.yml

on: pull_request
Typecheck
36s
Typecheck
Lint
31s
Lint
Prettier
34s
Prettier
Test
1m 6s
Test
Build
57s
Build
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Unhandled error: packages/js-sdk/test/Client.test.ts#L377
AssertionError: promise resolved "undefined" instead of rejecting - Expected + Received - [Error: rejected promise] + undefined ❯ Assertion.__VITEST_REJECTS__ ../../node_modules/@vitest/expect/dist/index.js:1794:21 ❯ Assertion.propertyGetter ../../node_modules/chai/chai.js:1466:29 ❯ Object.proxyGetter [as get] ../../node_modules/chai/chai.js:1550:22 ❯ test/Client.test.ts:377:42 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 ❯ runTest ../../node_modules/@vitest/runner/dist/index.js:939:11 ❯ runSuite ../../node_modules/@vitest/runner/dist/index.js:1095:15 ❯ runSuite ../../node_modules/@vitest/runner/dist/index.js:1095:15 ❯ runFiles ../../node_modules/@vitest/runner/dist/index.js:1152:5 This error originated in "test/Client.test.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 "Default/empty options". 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.
Unhandled error: packages/js-sdk/test/ApiClientE2E.test.ts#L56
AssertionError: promise resolved "{}" instead of rejecting - Expected + Received - [Error: rejected promise] + Object {} ❯ Assertion.__VITEST_REJECTS__ ../../node_modules/@vitest/expect/dist/index.js:1794:21 ❯ Assertion.propertyGetter ../../node_modules/chai/chai.js:1466:29 ❯ Object.proxyGetter [as get] ../../node_modules/chai/chai.js:1550:22 ❯ test/ApiClientE2E.test.ts:56:9 ❯ ../../node_modules/@vitest/runner/dist/index.js:146:14 ❯ ../../node_modules/@vitest/runner/dist/index.js:61:7 ❯ runTest ../../node_modules/@vitest/runner/dist/index.js:939:17 ❯ runSuite ../../node_modules/@vitest/runner/dist/index.js:1095:15 ❯ runSuite ../../node_modules/@vitest/runner/dist/index.js:1095:15 This error originated in "test/ApiClientE2E.test.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 "publish success". 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/ApiClientE2E.test.ts > e2e tests > local docker node > publish restricted topic: packages/js-sdk/test/ApiClientE2E.test.ts#L56
AssertionError: promise resolved "{}" instead of rejecting - Expected + Received - [Error: rejected promise] + Object {} ❯ test/ApiClientE2E.test.ts:56:9
test/Client.test.ts > publishEnvelopes > rejects with invalid envelopes: packages/js-sdk/test/Client.test.ts#L377
AssertionError: promise resolved "undefined" instead of rejecting - Expected: [Error: rejected promise] + Received: undefined ❯ test/Client.test.ts:377:42
Test
Process completed with exit code 1.