feat(e2e-cli): add flush-retry loop to simulate real flush policy #39
Annotations
10 errors and 1 warning
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 5xx Server Errors - Non-Retryable Exceptions > drops batch on 505 HTTP Version Not Supported:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L296
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:296:57
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 5xx Server Errors - Non-Retryable Exceptions > drops batch on 501 Not Implemented:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L283
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:283:57
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 4xx Client Errors - Retryable Exceptions > retries on 429 Too Many Requests with Retry-After:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L169
AssertionError: expected 105 to be greater than or equal to 900
❯ src/tests/retry/http-status-codes.test.ts:169:23
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 4xx Client Errors - Non-Retryable (Drop Events) > drops batch on 422 Unprocessable Entity:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L110
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:110:57
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 4xx Client Errors - Non-Retryable (Drop Events) > drops batch on 404 Not Found:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L97
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:97:57
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 4xx Client Errors - Non-Retryable (Drop Events) > drops batch on 403 Forbidden:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L84
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:84:57
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 4xx Client Errors - Non-Retryable (Drop Events) > drops batch on 401 Unauthorized:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L71
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:71:57
|
|
src/tests/retry/http-status-codes.test.ts > HTTP Status Code Handling > 4xx Client Errors - Non-Retryable (Drop Events) > drops batch on 400 Bad Request:
sdk-e2e-tests/src/tests/retry/http-status-codes.test.ts#L55
AssertionError: expected [ { method: 'POST', …(4) }, …(1) ] to have a length of 1 but got 2
- Expected
+ Received
- 1
+ 2
❯ src/tests/retry/http-status-codes.test.ts:55:57
|
|
src/tests/retry/exponential-backoff.test.ts > Exponential Backoff > later delays grow larger than earlier ones:
sdk-e2e-tests/src/tests/retry/exponential-backoff.test.ts#L96
AssertionError: expected 102 to be greater than 103
❯ src/tests/retry/exponential-backoff.test.ts:96:23
|
|
src/tests/retry/exponential-backoff.test.ts > Exponential Backoff > retries with increasing delays:
sdk-e2e-tests/src/tests/retry/exponential-backoff.test.ts#L67
AssertionError: expected 102 to be greater than 105
❯ src/tests/retry/exponential-backoff.test.ts:67:23
|
|
e2e-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|