Skip to content

0.0.6

0.0.6 #26

Triggered via push July 29, 2023 21:36
Status Failure
Total duration 4m 12s
Artifacts

test.yml

on: push
Matrix: integration
Fit to window
Zoom out
Zoom in

Annotations

8 errors, 10 warnings, and 2 notices
[chromium] › basic.test.ts:61:2 › rendering › ssr: test/helpers/create-fixture.ts#L40
1) [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================= Error: Expected build directory to exist at /home/runner/work/vinxi/vinxi/test/.fixtures/rendering-09ohqp7qb98/.output/server/index.mjs. The build probably failed. Did you maybe have a syntax error in your test code strings? at helpers/create-fixture.ts:40 38 | let buildPath = path.resolve(projectDir, ".output", "server", "index.mjs"); 39 | if (!fse.existsSync(buildPath)) { > 40 | throw new Error( | ^ 41 | c.red( 42 | `Expected build directory to exist at ${c.dim( 43 | buildPath, at createFixture (file:///home/runner/work/vinxi/vinxi/test/helpers/create-fixture.ts:40:9) at file:///home/runner/work/vinxi/vinxi/test/basic.test.ts:17:13
[chromium] › basic.test.ts:61:2 › rendering › ssr: test/helpers/create-fixture.ts#L40
1) [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================= Retry #1 --------------------------------------------------------------------------------------- Error: Expected build directory to exist at /home/runner/work/vinxi/vinxi/test/.fixtures/rendering-4f731t023oo/.output/server/index.mjs. The build probably failed. Did you maybe have a syntax error in your test code strings? at helpers/create-fixture.ts:40 38 | let buildPath = path.resolve(projectDir, ".output", "server", "index.mjs"); 39 | if (!fse.existsSync(buildPath)) { > 40 | throw new Error( | ^ 41 | c.red( 42 | `Expected build directory to exist at ${c.dim( 43 | buildPath, at createFixture (file:///home/runner/work/vinxi/vinxi/test/helpers/create-fixture.ts:40:9) at file:///home/runner/work/vinxi/vinxi/test/basic.test.ts:17:13
[chromium] › basic.test.ts:61:2 › rendering › ssr: test/helpers/create-fixture.ts#L40
1) [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================= Retry #2 --------------------------------------------------------------------------------------- Error: Expected build directory to exist at /home/runner/work/vinxi/vinxi/test/.fixtures/rendering-p86vps02m88/.output/server/index.mjs. The build probably failed. Did you maybe have a syntax error in your test code strings? at helpers/create-fixture.ts:40 38 | let buildPath = path.resolve(projectDir, ".output", "server", "index.mjs"); 39 | if (!fse.existsSync(buildPath)) { > 40 | throw new Error( | ^ 41 | c.red( 42 | `Expected build directory to exist at ${c.dim( 43 | buildPath, at createFixture (file:///home/runner/work/vinxi/vinxi/test/helpers/create-fixture.ts:40:9) at file:///home/runner/work/vinxi/vinxi/test/basic.test.ts:17:13
👀 (os: ubuntu-latest, node: 18)
Process completed with exit code 1.
[chromium] › basic.test.ts:61:2 › rendering › ssr: test\helpers\create-fixture.ts#L40
1) [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================= Error: Expected build directory to exist at D:\a\vinxi\vinxi\test\.fixtures\rendering-8t4h5pr8j\.output\server\index.mjs. The build probably failed. Did you maybe have a syntax error in your test code strings? at helpers\create-fixture.ts:40 38 | let buildPath = path.resolve(projectDir, ".output", "server", "index.mjs"); 39 | if (!fse.existsSync(buildPath)) { > 40 | throw new Error( | ^ 41 | c.red( 42 | `Expected build directory to exist at ${c.dim( 43 | buildPath, at createFixture (file:///D:/a/vinxi/vinxi/test/helpers/create-fixture.ts:40:9) at file:///D:/a/vinxi/vinxi/test/basic.test.ts:17:13
[chromium] › basic.test.ts:61:2 › rendering › ssr: test\helpers\create-fixture.ts#L40
1) [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================= Retry #1 --------------------------------------------------------------------------------------- Error: Expected build directory to exist at D:\a\vinxi\vinxi\test\.fixtures\rendering-a450g2o33u8\.output\server\index.mjs. The build probably failed. Did you maybe have a syntax error in your test code strings? at helpers\create-fixture.ts:40 38 | let buildPath = path.resolve(projectDir, ".output", "server", "index.mjs"); 39 | if (!fse.existsSync(buildPath)) { > 40 | throw new Error( | ^ 41 | c.red( 42 | `Expected build directory to exist at ${c.dim( 43 | buildPath, at createFixture (file:///D:/a/vinxi/vinxi/test/helpers/create-fixture.ts:40:9) at file:///D:/a/vinxi/vinxi/test/basic.test.ts:17:13
[chromium] › basic.test.ts:61:2 › rendering › ssr: test\helpers\create-fixture.ts#L40
1) [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================= Retry #2 --------------------------------------------------------------------------------------- Error: Expected build directory to exist at D:\a\vinxi\vinxi\test\.fixtures\rendering-ld6m615cdtg\.output\server\index.mjs. The build probably failed. Did you maybe have a syntax error in your test code strings? at helpers\create-fixture.ts:40 38 | let buildPath = path.resolve(projectDir, ".output", "server", "index.mjs"); 39 | if (!fse.existsSync(buildPath)) { > 40 | throw new Error( | ^ 41 | c.red( 42 | `Expected build directory to exist at ${c.dim( 43 | buildPath, at createFixture (file:///D:/a/vinxi/vinxi/test/helpers/create-fixture.ts:40:9) at file:///D:/a/vinxi/vinxi/test/basic.test.ts:17:13
👀 (os: windows-latest, node: 18)
Process completed with exit code 1.
🎭 Playwright Run Summary
1 failed [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================== 1 skipped
🎭 Playwright Run Summary
1 failed [chromium] › basic.test.ts:61:2 › rendering › ssr ============================================== 1 skipped
👀 (os: ubuntu-latest, node: 18)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, pnpm/action-setup@v2.2.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
👀 (os: ubuntu-latest, node: 18)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: ubuntu-latest, node: 18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: ubuntu-latest, node: 18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: ubuntu-latest, node: 18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: windows-latest, node: 18)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, pnpm/action-setup@v2.2.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
👀 (os: windows-latest, node: 18)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: windows-latest, node: 18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: windows-latest, node: 18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
👀 (os: windows-latest, node: 18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/