e2e #540
bucketeer-botAnnotations
3 errors and 1 warning
|
e2e/events.spec.ts > e2e/events > goal event:
src/internal/remote/toBKTException.ts#L70
ServiceUnavailableException: upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: Connection refused
❯ toBKTException src/internal/remote/toBKTException.ts:70:13
❯ src/internal/remote/post.ts:37:10
❯ postInternal src/internal/remote/post.ts:17:17
❯ ApiClientImpl.registerEvents src/internal/remote/ApiClient.ts:94:18
❯ EventInteractor.sendEvents src/internal/event/EventInteractor.ts:214:19
❯ BKTClientImpl.flush src/BKTClient.ts:184:19
❯ e2e/events.spec.ts:73:4
|
|
e2e/events.spec.ts > e2e/events > MetricsEvent > Using a random string in the api key setting should throw Forbidden:
e2e/events.spec.ts#L212
AssertionError: expected error to be instance of ForbiddenException
- Expected:
[Function ForbiddenException]
+ Received:
[ServiceUnavailableException: upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: Connection refused]
❯ e2e/events.spec.ts:212:6
|
|
ci
Process completed with exit code 1.
|
|
ci
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|