3.0.1 #2
Triggered via release
January 19, 2026 02:46
andrekutianski
created
3.0.1
Status
Failure
Total duration
1m 14s
Artifacts
–
Annotations
14 errors
|
Publish Package
Process completed with exit code 1.
|
|
tests/unit/service-invoices.test.ts > ServiceInvoicesResource > createAndWait > should extract path from full URL in location header:
tests/unit/service-invoices.test.ts#L518
AssertionError: expected "spy" to be called with arguments: [ Array(1) ]
Received:
1st spy call:
Array [
- "/v1/companies/test-company-id/serviceinvoices/test-invoice-id",
+ "/companies/test-company-id/serviceinvoices/test-invoice-id",
]
Number of calls: 1
❯ tests/unit/service-invoices.test.ts:518:34
|
|
tests/unit/service-invoices.test.ts > ServiceInvoicesResource > createAndWait > should throw InvoiceProcessingError on unexpected response format:
tests/unit/service-invoices.test.ts#L424
AssertionError: promise resolved "{ code: 200, …(1) }" instead of rejecting
- Expected
+ Received
- [Error: rejected promise]
+ Object {
+ "code": 200,
+ "message": "Unexpected response",
+ }
❯ tests/unit/service-invoices.test.ts:424:7
|
|
tests/unit/http-client.test.ts > HttpClient > Authentication > should include Basic Auth header:
tests/unit/http-client.test.ts#L212
AssertionError: expected undefined to be 'test-api-key-12345' // Object.is equality
- Expected:
"test-api-key-12345"
+ Received:
undefined
❯ tests/unit/http-client.test.ts:212:26
|
|
tests/unit/client-polling-integration.test.ts > Client Polling Integration > end-to-end invoice creation with polling > should handle network errors during polling and retry:
tests/unit/client-polling-integration.test.ts#L165
Error: Network timeout
❯ tests/unit/client-polling-integration.test.ts:165:32
|
|
Unhandled error:
src/core/utils/polling.ts#L243
Error: Polling failed after 3 attempts
❯ Module.pollWithRetries src/core/utils/polling.ts:243:9
This error originated in "tests/unit/core/utils/polling.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 throw after max attempts". 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:
src/core/utils/polling.ts#L123
TimeoutError: Polling timeout exceeded after 4 attempts (4750ms)
❯ Module.poll src/core/utils/polling.ts:123:15
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: undefined, details: 408 }
This error originated in "tests/unit/core/utils/polling.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 throw TimeoutError when timeout exceeded". 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.
|
|
Publish Package
Process completed with exit code 1.
|
|
tests/unit/service-invoices.test.ts > ServiceInvoicesResource > createAndWait > should extract path from full URL in location header:
tests/unit/service-invoices.test.ts#L518
AssertionError: expected "spy" to be called with arguments: [ Array(1) ]
Received:
1st spy call:
Array [
- "/v1/companies/test-company-id/serviceinvoices/test-invoice-id",
+ "/companies/test-company-id/serviceinvoices/test-invoice-id",
]
Number of calls: 1
❯ tests/unit/service-invoices.test.ts:518:34
|
|
tests/unit/service-invoices.test.ts > ServiceInvoicesResource > createAndWait > should throw InvoiceProcessingError on unexpected response format:
tests/unit/service-invoices.test.ts#L424
AssertionError: promise resolved "{ code: 200, …(1) }" instead of rejecting
- Expected
+ Received
- [Error: rejected promise]
+ Object {
+ "code": 200,
+ "message": "Unexpected response",
+ }
❯ tests/unit/service-invoices.test.ts:424:7
|
|
tests/unit/http-client.test.ts > HttpClient > Authentication > should include Basic Auth header:
tests/unit/http-client.test.ts#L212
AssertionError: expected undefined to be 'test-api-key-12345' // Object.is equality
- Expected:
"test-api-key-12345"
+ Received:
undefined
❯ tests/unit/http-client.test.ts:212:26
|
|
tests/unit/client-polling-integration.test.ts > Client Polling Integration > end-to-end invoice creation with polling > should handle network errors during polling and retry:
tests/unit/client-polling-integration.test.ts#L165
Error: Network timeout
❯ tests/unit/client-polling-integration.test.ts:165:32
|
|
Unhandled error:
src/core/utils/polling.ts#L243
Error: Polling failed after 3 attempts
❯ Module.pollWithRetries src/core/utils/polling.ts:243:9
This error originated in "tests/unit/core/utils/polling.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 throw after max attempts". 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:
src/core/utils/polling.ts#L123
TimeoutError: Polling timeout exceeded after 4 attempts (4750ms)
❯ Module.poll src/core/utils/polling.ts:123:15
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: undefined, details: 408 }
This error originated in "tests/unit/core/utils/polling.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 throw TimeoutError when timeout exceeded". 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.
|