Skip to content

vitest-ecosystem-ci #240

vitest-ecosystem-ci

vitest-ecosystem-ci #240

Triggered via schedule January 15, 2025 05:14
Status Failure
Total duration 20m 39s
Artifacts

ecosystem-ci.yml

on: schedule
Matrix: test-ecosystem
Fit to window
Zoom out
Zoom in

Annotations

21 errors and 17 warnings
test-ecosystem (vitest-browser-examples)
Process completed with exit code 1.
test-ecosystem (vitest-browser-simple)
Process completed with exit code 1.
test-ecosystem (vitest-github-actions-reporter)
Property 'type' does not exist on type 'never'.
test-ecosystem (vitest-github-actions-reporter)
Property 'type' does not exist on type 'never'.
test-ecosystem (vitest-github-actions-reporter)
Process completed with exit code 1.
test-ecosystem (nuxt)
Property 'loadNuxt' does not exist on type 'typeof import("/home/runner/work/vitest-ecosystem-ci/vitest-ecosystem-ci/workspace/nuxt/nuxt/packages/nuxt/types")'.
test-ecosystem (nuxt)
Property 'build' does not exist on type 'typeof import("/home/runner/work/vitest-ecosystem-ci/vitest-ecosystem-ci/workspace/nuxt/nuxt/packages/nuxt/types")'.
test-ecosystem (nuxt)
Property 'loadNuxt' does not exist on type 'typeof import("/home/runner/work/vitest-ecosystem-ci/vitest-ecosystem-ci/workspace/nuxt/nuxt/packages/nuxt/types")'.
test-ecosystem (nuxt)
Property 'build' does not exist on type 'typeof import("/home/runner/work/vitest-ecosystem-ci/vitest-ecosystem-ci/workspace/nuxt/nuxt/packages/nuxt/types")'.
test-ecosystem (nuxt)
Process completed with exit code 1.
test-ecosystem (nuxt-test-utils)
Process completed with exit code 1.
test/BigInt.test.ts > BigInt > sqrt: workspace/effect/effect/packages/effect/test/BigInt.test.ts#L141
AssertionError: expected a thrown error to be Error: Cannot take the square root of a n… - Expected + Received - Error { + RangeError { "message": "Cannot take the square root of a negative number", } ❯ test/BigInt.test.ts:141:43
test/Schema/ParseResult.test.ts > ParseIssue.actual > asserts: workspace/effect/effect/packages/effect/test/Schema/ParseResult.test.ts#L254
AssertionError: expected a thrown error to be Error: Expected string, actual 1 - Expected + Received - Error { + ParseError { "message": "Expected string, actual 1", + "issue": Type { + "_tag": "Type", + "actual": 1, + "ast": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + "message": undefined, + }, + "_tag": "ParseError", } ❯ test/Schema/ParseResult.test.ts:254:40
test/Schema/ParseResultFormatter.test.ts > ParseResultFormatter > Forbidden > default message: workspace/effect/effect/packages/effect/test/Schema/ParseResultFormatter.test.ts#L27
AssertionError: expected a thrown error to be Error: (string <-> string) └─ cannot be b… - Expected + Received - Error { + ParseError { "message": "(string <-> string) └─ cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + "issue": Forbidden { + "_tag": "Forbidden", + "actual": "", + "ast": { + "_tag": "Transformation", + "annotations": {}, + "from": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + "to": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + }, + "message": "cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + }, + "_tag": "ParseError", } ❯ test/Schema/ParseResultFormatter.test.ts:27:56
test/Schema/ParseResultFormatter.test.ts > ParseResultFormatter > Forbidden > default message with identifier: workspace/effect/effect/packages/effect/test/Schema/ParseResultFormatter.test.ts#L44
AssertionError: expected a thrown error to be Error: identifier └─ cannot be be resolve… - Expected + Received - Error { + ParseError { "message": "identifier └─ cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + "issue": Forbidden { + "_tag": "Forbidden", + "actual": "", + "ast": { + "_tag": "Transformation", + "annotations": { + "Symbol(effect/annotation/Identifier)": "identifier", + }, + "from": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + "to": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + }, + "message": "cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + }, + "_tag": "ParseError", } ❯ test/Schema/ParseResultFormatter.test.ts:44:56
test/Schema/ParseResultFormatter.test.ts > ParseResultFormatter > Forbidden > custom message (override=false): workspace/effect/effect/packages/effect/test/Schema/ParseResultFormatter.test.ts#L61
AssertionError: expected a thrown error to be Error: (string <-> string) └─ cannot be b… - Expected + Received - Error { + ParseError { "message": "(string <-> string) └─ cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + "issue": Forbidden { + "_tag": "Forbidden", + "actual": "", + "ast": { + "_tag": "Transformation", + "annotations": { + "Symbol(effect/annotation/Message)": [Function message], + }, + "from": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + "to": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + }, + "message": "cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + }, + "_tag": "ParseError", } ❯ test/Schema/ParseResultFormatter.test.ts:61:56
test/Schema/ParseResultFormatter.test.ts > ParseResultFormatter > Forbidden > custom message (override=true): workspace/effect/effect/packages/effect/test/Schema/ParseResultFormatter.test.ts#L78
AssertionError: expected a thrown error to be Error: (string <-> string) └─ cannot be b… - Expected + Received - Error { + ParseError { "message": "(string <-> string) └─ cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + "issue": Forbidden { + "_tag": "Forbidden", + "actual": "", + "ast": { + "_tag": "Transformation", + "annotations": { + "Symbol(effect/annotation/Message)": [Function message], + }, + "from": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + "to": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + }, + "message": "cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + }, + "_tag": "ParseError", } ❯ test/Schema/ParseResultFormatter.test.ts:78:56
test/Schema/Schema/DecodingFallbackAnnotation.test.ts > DecodingFallbackAnnotation > using an async Effect: workspace/effect/effect/packages/effect/test/Schema/Schema/DecodingFallbackAnnotation.test.ts#L49
AssertionError: expected a thrown error to be Error: string └─ cannot be be resolved sy… - Expected + Received - Error { + ParseError { "message": "string └─ cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + "issue": Forbidden { + "_tag": "Forbidden", + "actual": null, + "ast": { + "_tag": "StringKeyword", + "annotations": { + "Symbol(effect/annotation/DecodingFallback)": [Function decodingFallback], + "Symbol(effect/annotation/Description)": "a string", + "Symbol(effect/annotation/Title)": "string", + }, + }, + "message": "cannot be be resolved synchronously, this is caused by using runSync on an effect that performs async work", + }, + "_tag": "ParseError", } ❯ test/Schema/Schema/DecodingFallbackAnnotation.test.ts:49:53
test/Schema/Schema/ParseOptions-exact.test.ts > `exact` option > asserts > true (default): workspace/effect/effect/packages/effect/test/Schema/TestUtils.ts#L377
AssertionError: expected a thrown error to be Error: { readonly a: unknown } └─ ["a"] … - Expected + Received - Error { + ParseError { "message": "{ readonly a: unknown } └─ [\"a\"] └─ is missing", + "issue": Composite { + "_tag": "Composite", + "actual": {}, + "ast": { + "_tag": "TypeLiteral", + "annotations": {}, + "indexSignatures": [], + "propertySignatures": [ + { + "annotations": {}, + "isOptional": false, + "isReadonly": true, + "name": "a", + "type": { + "_tag": "UnknownKeyword", + "annotations": { + "Symbol(effect/annotation/Title)": "unknown", + }, + }, + }, + ], + }, + "issues": Pointer { + "_tag": "Pointer", + "actual": {}, + "issue": Missing { + "_tag": "Missing", + "actual": undefined, + "ast": { + "annotations": {}, + "isOptional": false, + "isReadonly": true, + "name": "a", + "type": { + "_tag": "UnknownKeyword", + "annotations": { + "Symbol(effect/annotation/Title)": "unknown", + }, + }, + }, + "message": undefined, + }, + "path": "a", + }, + "output": {}, + }, + "_tag": "ParseError", } ❯ Module.expectAssertsFailure test/Schema/TestUtils.ts:377:51 ❯ test/Schema/Schema/ParseOptions-exact.test.ts:40:12
test/Schema/Schema/asserts.test.ts > asserts > should respect outer/inner options: workspace/effect/effect/packages/effect/test/Schema/Schema/asserts.test.ts#L19
AssertionError: expected a thrown error to be Error: { readonly a: number } └─ ["b"] … - Expected + Received - Error { + ParseError { "message": "{ readonly a: number } └─ [\"b\"] └─ is unexpected, expected: \"a\"", + "issue": Composite { + "_tag": "Composite", + "actual": { + "a": 1, + "b": "b", + }, + "ast": { + "_tag": "TypeLiteral", + "annotations": {}, + "indexSignatures": [], + "propertySignatures": [ + { + "annotations": {}, + "isOptional": false, + "isReadonly": true, + "name": "a", + "type": { + "_tag": "NumberKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a number", + "Symbol(effect/annotation/Title)": "number", + }, + }, + }, + ], + }, + "issues": Pointer { + "_tag": "Pointer", + "actual": { + "a": 1, + "b": "b", + }, + "issue": Unexpected { + "_tag": "Unexpected", + "actual": "b", + "message": "is unexpected, expected: \"a\"", + }, + "path": "b", + }, + "output": {}, + }, + "_tag": "ParseError", } ❯ test/Schema/Schema/asserts.test.ts:19:75
test/Schema/Schema/asserts.test.ts > asserts > struct > required property signature: workspace/effect/effect/packages/effect/test/Schema/TestUtils.ts#L377
AssertionError: expected a thrown error to be Error: { readonly a: number } └─ ["a"] … - Expected + Received - Error { + ParseError { "message": "{ readonly a: number } └─ [\"a\"] └─ Expected number, actual null", + "issue": Composite { + "_tag": "Composite", + "actual": { + "a": null, + }, + "ast": { + "_tag": "TypeLiteral", + "annotations": {}, + "indexSignatures": [], + "propertySignatures": [ + { + "annotations": {}, + "isOptional": false, + "isReadonly": true, + "name": "a", + "type": { + "_tag": "NumberKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a number", + "Symbol(effect/annotation/Title)": "number", + }, + }, + }, + ], + }, + "issues": Pointer { + "_tag": "Pointer", + "actual": { + "a": null, + }, + "issue": Type { + "_tag": "Type", + "actual": null, + "ast": { + "_tag": "NumberKeyword", + "annotations": { + "Symbol(effect/annotation/Description)": "a number", + "Symbol(effect/annotation/Title)": "number", + }, + }, + "message": undefined, + }, + "path": "a", + }, + "output": {}, + }, + "_tag": "ParseError", } ❯ Module.expectAssertsFailure test/Schema/TestUtils.ts:377:51 ❯ test/Schema/Schema/asserts.test.ts:37:12
test-ecosystem (vitest-browser-examples)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-browser-simple)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-github-actions-reporter)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (zustand)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (aria-live-capture)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (nuxt)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-reporters-large)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (elk)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (lerna-lite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (nuxt-test-utils)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-sonar-reporter)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vue)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-vscode)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (effect)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-benchmark-large)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-ecosystem (vitest-coverage-large)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636