Debugging Tests #366
test.yaml
on: pull_request
Upstash Workflow Tests
1m 48s
CF Workers Local Build
42s
CF Workers (Hono) Local Build
41s
Express Local Build
41s
Hono Local Build
40s
Image Gen Local Build
55s
Cross Reference Agent Local Build
1m 16s
Nextjs Local Build
1m 6s
Nextjs (Node 18) Local Build
47s
Nextjs Pages Local Build
1m 16s
Nuxt Local Build
1m 32s
Sveltekit Local Build
1m 17s
Solidjs Local Build
0s
integration-test
13m 47s
cloudflare-workers-hono-deployed
2m 36s
nextjs12-node18-deployed
2m 5s
nextjs-pages-deployed
3m 16s
sveltekit-deployed
3m 5s
express-deployed
2m 8s
Annotations
18 errors and 1 warning
error: Test "should return undefined from empty string" timed out after 25897ms
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
|
cloudflare-workers-hono-deployed
Process completed with exit code 1.
|
error: Test "should return undefined from undefined string" timed out after 25889ms
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
|
error: Test "should return foo correctly" timed out after 25960ms
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
|
error: Test "should allow json object" timed out after 25904ms
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
|
sveltekit-deployed
Process completed with exit code 1.
|
error: Test "should return undefined from empty string" timed out after 25594ms
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
|
nextjs-pages-deployed
Process completed with exit code 1.
|
Unhandled error:
examples/ci/app/ci/upstash/redis.ts#L135
Error: result not found for route some-route with randomTestId some-id
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:135:11
❯ processTicksAndRejections node:internal/process/task_queues:95:5
This error originated in "app/ci/upstash/redis.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
|
Unhandled error:
examples/ci/app/ci/upstash/redis.ts#L44
Error: callCount shouldn't be 0. It was 0 in test of the route 'some-route'
❯ Module.saveResultsWithoutContext app/ci/upstash/redis.ts:44:11
❯ processTicksAndRejections node:internal/process/task_queues:95:5
This error originated in "app/ci/upstash/redis.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
|
Unhandled error:
examples/ci/app/ci/utils.ts#L98
Error: Unexpected value.
Received "random-result-4130"
Expected "not-correct"
❯ expect app/ci/utils.ts:98:11
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:147:3
❯ processTicksAndRejections node:internal/process/task_queues:95:5
This error originated in "app/ci/upstash/redis.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 "should override call count". 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:
examples/ci/app/ci/utils.ts#L98
Error: Unexpected value.
Received "2"
Expected "123"
❯ expect app/ci/utils.ts:98:11
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:148:3
❯ processTicksAndRejections node:internal/process/task_queues:95:5
This error originated in "app/ci/upstash/redis.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 "should override call count". 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:
examples/ci/app/ci/utils.ts#L98
Error: Unexpected value.
Received "-3"
Expected "3"
❯ expect app/ci/utils.ts:98:11
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:148:3
❯ processTicksAndRejections node:internal/process/task_queues:95:5
This error originated in "app/ci/upstash/redis.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 "should fail if marked as failed". 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.
|
app/ci/ci.test.ts > workflow integration tests > call/workflow:
examples/ci/app/ci/upstash/redis.ts#L135
Error: result not found for route call/workflow with randomTestId 7045
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:135:11
❯ initiateTest app/ci/utils.ts:89:3
❯ timeout app/ci/ci.test.ts:10:9
|
app/ci/ci.test.ts > workflow integration tests > wait-for-event/workflow:
examples/ci/app/ci/upstash/redis.ts#L135
Error: result not found for route wait-for-event/workflow with randomTestId 1669
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:135:11
❯ initiateTest app/ci/utils.ts:89:3
❯ timeout app/ci/ci.test.ts:10:9
|
app/ci/ci.test.ts > workflow integration tests > invoke/workflows/workflowOne:
examples/ci/app/ci/upstash/redis.ts#L135
Error: result not found for route invoke/workflows/workflowOne with randomTestId 9409
❯ Module.checkRedisForResults app/ci/upstash/redis.ts:135:11
❯ initiateTest app/ci/utils.ts:89:3
❯ timeout app/ci/ci.test.ts:10:9
|
app/ci/upstash/redis.test.ts > redis > should throw on missing results:
examples/ci/app/ci/upstash/redis.test.ts#L9
AssertionError: expected [Function] to throw an error
- Expected:
null
+ Received:
undefined
❯ timeout app/ci/upstash/redis.test.ts:9:7
|
app/ci/upstash/redis.test.ts > redis > should throw when saving results without any increment:
examples/ci/app/ci/upstash/redis.test.ts#L17
AssertionError: expected [Function] to throw an error
- Expected:
null
+ Received:
undefined
❯ app/ci/upstash/redis.test.ts:17:7
|
Release
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/
|