ci: fix force ipv4 on gh #135
build-and-release.yaml
on: push
Matrix: build-and-release-electron
Matrix: build-and-release-nodejs
Annotations
54 errors and 58 warnings
build-and-release-electron (macos-14, 7.86.0, 20, 28.3.3)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
build-and-release-electron (macos-14, 7.86.0, 20, 33.2.1)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
build-and-release-electron (macos-14, 7.86.0, 20, 26.6.2)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
build-and-release-electron (macos-14, 7.86.0, 20, 27.1.3)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
build-and-release-electron (macos-14, 7.86.0, 20, 31.7.5)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
build-and-release-electron (macos-14, 7.86.0, 20, 32.2.6)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 21)
Process completed with exit code 1.
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 22)
Process completed with exit code 1.
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 18)
Process completed with exit code 1.
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 20)
Process completed with exit code 1.
|
build-and-release-nodejs (macos-14, 7.86.0, 18)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
Unhandled error:
test/curl/callbacks.spec.ts#L136
AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 not accept undefined return". 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:
test/curl/callbacks.spec.ts#L222
AssertionError: expected 7 to be 42 // Object.is equality
- Expected
+ Received
- 42
+ 7
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on false". 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:
test/curl/callbacks.spec.ts#L254
AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality
Expected: "thrown error inside callback"
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L287
AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality
Expected: "Return value from the Trailer callback must be an array of strings or false."
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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:
test/curl/callbacks.spec.ts#L339
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on Abort return value". 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:
test/curl/callbacks.spec.ts#L363
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L389
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31
❯ Curl.emit node:events:517:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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.
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParsers:
test/curl/curly.spec.ts#L269
AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server'
- Expected:
/^Response body parser for/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:269:7
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParser:
test/curl/curly.spec.ts#L281
AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server'
- Expected:
/^`curlyResponseBodyParser` passed to curly must be/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:281:7
|
test/curl/curly.spec.ts > curly > error handling > error thrown inside response body parser bubble up to the original call:
test/curl/curly.spec.ts#L295
AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server'
- Expected:
/^error here/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:295:7
|
build-and-release-nodejs (macos-14, 7.86.0, 22)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
Unhandled error:
test/curl/callbacks.spec.ts#L136
AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 not accept undefined return". 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:
test/curl/callbacks.spec.ts#L222
AssertionError: expected 7 to be 42 // Object.is equality
- Expected
+ Received
- 42
+ 7
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on false". 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:
test/curl/callbacks.spec.ts#L254
AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality
Expected: "thrown error inside callback"
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L287
AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality
Expected: "Return value from the Trailer callback must be an array of strings or false."
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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:
test/curl/callbacks.spec.ts#L339
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on Abort return value". 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:
test/curl/callbacks.spec.ts#L363
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L389
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31
❯ Curl.emit node:events:524:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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.
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParsers:
test/curl/curly.spec.ts#L269
AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server'
- Expected:
/^Response body parser for/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:269:7
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParser:
test/curl/curly.spec.ts#L281
AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server'
- Expected:
/^`curlyResponseBodyParser` passed to curly must be/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:281:7
|
test/curl/curly.spec.ts > curly > error handling > error thrown inside response body parser bubble up to the original call:
test/curl/curly.spec.ts#L295
AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server'
- Expected:
/^error here/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:295:7
|
build-and-release-nodejs (macos-14, 7.86.0, 20)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
Unhandled error:
test/curl/callbacks.spec.ts#L136
AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 not accept undefined return". 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:
test/curl/callbacks.spec.ts#L222
AssertionError: expected 7 to be 42 // Object.is equality
- Expected
+ Received
- 42
+ 7
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on false". 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:
test/curl/callbacks.spec.ts#L254
AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality
Expected: "thrown error inside callback"
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L287
AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality
Expected: "Return value from the Trailer callback must be an array of strings or false."
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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:
test/curl/callbacks.spec.ts#L339
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on Abort return value". 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:
test/curl/callbacks.spec.ts#L363
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L389
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31
❯ Curl.emit node:events:518:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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.
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParsers:
test/curl/curly.spec.ts#L269
AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server'
- Expected:
/^Response body parser for/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:269:7
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParser:
test/curl/curly.spec.ts#L281
AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server'
- Expected:
/^`curlyResponseBodyParser` passed to curly must be/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:281:7
|
test/curl/curly.spec.ts > curly > error handling > error thrown inside response body parser bubble up to the original call:
test/curl/curly.spec.ts#L295
AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server'
- Expected:
/^error here/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:295:7
|
build-and-release-nodejs (macos-14, 7.86.0, 21)
SHA256 mismatch
Expected: 35af6cc88cd680698652b3edc8a1553e7e58cce0fc946d34d2cabd66c4e3db44
Actual: 1cc6d8a35452216165000266e13a03ac893dfc6b13302ea226fea6357c907a6d
File: /Users/runner/Library/Caches/Homebrew/downloads/f94a296e06e4ee48ef869cd45f5258616710853f5dac8c69d96782f249d208ff--Cloudflare_WARP_2024.12.554.0.pkg
To retry an incomplete download, remove the file above.
|
Unhandled error:
test/curl/callbacks.spec.ts#L136
AssertionError: expected Error: Couldn't connect to server to be an instance of TypeError
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:1336:17
❯ Proxy.<anonymous> node_modules/@vitest/expect/dist/index.js:972:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1610:25
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:136:25
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 not accept undefined return". 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:
test/curl/callbacks.spec.ts#L222
AssertionError: expected 7 to be 42 // Object.is equality
- Expected
+ Received
- 42
+ 7
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:222:31
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on false". 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:
test/curl/callbacks.spec.ts#L254
AssertionError: expected 'Couldn\'t connect to server' to be 'thrown error inside callback' // Object.is equality
Expected: "thrown error inside callback"
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:254:35
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L287
AssertionError: expected 'Couldn\'t connect to server' to be 'Return value from the Trailer callbac…' // Object.is equality
Expected: "Return value from the Trailer callback must be an array of strings or false."
Received: "Couldn't connect to server"
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:287:35
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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:
test/curl/callbacks.spec.ts#L339
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:339:31
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 abort request on Abort return value". 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:
test/curl/callbacks.spec.ts#L363
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:363:31
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 rethrow error thrown inside callback". 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:
test/curl/callbacks.spec.ts#L389
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ Curl.<anonymous> test/curl/callbacks.spec.ts:389:31
❯ Curl.emit node:events:519:28
❯ Curl.onError lib/Curl.ts:312:10
❯ Easy.<anonymous> lib/Curl.ts:101:19
This error originated in "test/curl/callbacks.spec.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 an error on invalid return value". 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.
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParsers:
test/curl/curly.spec.ts#L269
AssertionError: expected [Function] to throw error matching /^Response body parser for/ but got 'Couldn\'t connect to server'
- Expected:
/^Response body parser for/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:269:7
|
test/curl/curly.spec.ts > curly > error handling > throw error on invalid response body parser in option curlyResponseBodyParser:
test/curl/curly.spec.ts#L281
AssertionError: expected [Function] to throw error matching /^`curlyResponseBodyParser` passed to …/ but got 'Couldn\'t connect to server'
- Expected:
/^`curlyResponseBodyParser` passed to curly must be/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:281:7
|
test/curl/curly.spec.ts > curly > error handling > error thrown inside response body parser bubble up to the original call:
test/curl/curly.spec.ts#L295
AssertionError: expected [Function] to throw error matching /^error here/ but got 'Couldn\'t connect to server'
- Expected:
/^error here/
+ Received:
"Couldn't connect to server"
❯ test/curl/curly.spec.ts:295:7
|
build-and-release-electron (macos-14, 7.86.0, 20, 28.3.3)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-electron (macos-14, 7.86.0, 20, 28.3.3)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-electron (macos-14, 7.86.0, 20, 28.3.3)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-electron (macos-14, 7.86.0, 20, 28.3.3)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 28.3.3)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 33.2.1)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 33.2.1)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-electron (macos-14, 7.86.0, 20, 33.2.1)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-electron (macos-14, 7.86.0, 20, 33.2.1)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-electron (macos-14, 7.86.0, 20, 33.2.1)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 26.6.2)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 26.6.2)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-electron (macos-14, 7.86.0, 20, 26.6.2)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-electron (macos-14, 7.86.0, 20, 26.6.2)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-electron (macos-14, 7.86.0, 20, 26.6.2)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 27.1.3)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 27.1.3)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-electron (macos-14, 7.86.0, 20, 27.1.3)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-electron (macos-14, 7.86.0, 20, 27.1.3)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-electron (macos-14, 7.86.0, 20, 27.1.3)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 31.7.5)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-electron (macos-14, 7.86.0, 20, 31.7.5)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-electron (macos-14, 7.86.0, 20, 31.7.5)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-electron (macos-14, 7.86.0, 20, 31.7.5)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 31.7.5)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 32.2.6)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-electron (macos-14, 7.86.0, 20, 32.2.6)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-electron (macos-14, 7.86.0, 20, 32.2.6)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-electron (macos-14, 7.86.0, 20, 32.2.6)
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/
|
build-and-release-electron (macos-14, 7.86.0, 20, 32.2.6)
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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 21)
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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 21)
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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 22)
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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 22)
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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 20)
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/
|
build-and-release-nodejs (ubuntu-20.04, 7.86.0, 20)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 18)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-nodejs (macos-14, 7.86.0, 18)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-nodejs (macos-14, 7.86.0, 18)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-nodejs (macos-14, 7.86.0, 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/
|
build-and-release-nodejs (macos-14, 7.86.0, 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/
|
build-and-release-nodejs (macos-14, 7.86.0, 22)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 22)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-nodejs (macos-14, 7.86.0, 22)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-nodejs (macos-14, 7.86.0, 22)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-nodejs (macos-14, 7.86.0, 22)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 20)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 20)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-nodejs (macos-14, 7.86.0, 20)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-nodejs (macos-14, 7.86.0, 20)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
build-and-release-nodejs (macos-14, 7.86.0, 20)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 21)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 21)
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/
|
build-and-release-nodejs (macos-14, 7.86.0, 21)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
|
build-and-release-nodejs (macos-14, 7.86.0, 21)
wget 1.25.0 is already installed and up-to-date.
To reinstall 1.25.0, run:
brew reinstall wget
|
build-and-release-nodejs (macos-14, 7.86.0, 21)
cmake 3.31.2 is already installed and up-to-date.
To reinstall 3.31.2, run:
brew reinstall cmake
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
build-logs-macos-14-7.86.0-18
Expired
|
216 KB |
|
build-logs-macos-14-7.86.0-20
Expired
|
216 KB |
|
build-logs-macos-14-7.86.0-21
Expired
|
216 KB |
|
build-logs-macos-14-7.86.0-22
Expired
|
216 KB |
|
build-logs-macos-14-7.86.0-26.6.2
Expired
|
1.64 KB |
|
build-logs-macos-14-7.86.0-27.1.3
Expired
|
1.64 KB |
|
build-logs-macos-14-7.86.0-28.3.3
Expired
|
1.64 KB |
|
build-logs-macos-14-7.86.0-31.7.5
Expired
|
1.64 KB |
|
build-logs-macos-14-7.86.0-32.2.6
Expired
|
1.64 KB |
|
build-logs-macos-14-7.86.0-33.2.1
Expired
|
1.64 KB |
|
build-logs-ubuntu-20.04-7.86.0-18
Expired
|
113 KB |
|
build-logs-ubuntu-20.04-7.86.0-20
Expired
|
113 KB |
|
build-logs-ubuntu-20.04-7.86.0-21
Expired
|
113 KB |
|
build-logs-ubuntu-20.04-7.86.0-22
Expired
|
113 KB |
|