3.3.0 remove a layer of indirection (unnecessary passthrough) #264
Annotations
6 errors
Unhandled error:
tests/index.test.ts#L65
AssertionError: expected { '0': 'pipe:[40054]', …(19) } to strictly equal { '0': 'pipe:[40054]', …(18) }
- Expected
+ Received
Object {
"0": "pipe:[40054]",
"1": "pipe:[40055]",
"10": "pipe:[38545]",
"11": "pipe:[38545]",
"114": "pipe:[38214]",
"117": "pipe:[38215]",
"14": "pipe:[41048]",
"15": "pipe:[41048]",
"19": "pipe:[41076]",
"2": "pipe:[40056]",
"20": "pipe:[41076]",
"23": "pipe:[38554]",
"24": "pipe:[38554]",
"29": "pipe:[41077]",
"30": "pipe:[41077]",
+ "32": "/dev/ptmx",
"4": "pipe:[41046]",
"5": "pipe:[41046]",
"6": "pipe:[41047]",
"7": "pipe:[41047]",
}
❯ onExit tests/index.test.ts:65:34
❯ wrapper.ts:93:9
This error originated in "tests/index.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 "spawns and exits". 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:
tests/index.test.ts#L117
AssertionError: expected { '0': 'pipe:[40054]', …(19) } to strictly equal { '0': 'pipe:[40054]', …(18) }
- Expected
+ Received
Object {
"0": "pipe:[40054]",
"1": "pipe:[40055]",
"10": "pipe:[38545]",
"11": "pipe:[38545]",
"114": "pipe:[38214]",
"117": "pipe:[38215]",
"14": "pipe:[41048]",
"15": "pipe:[41048]",
"19": "pipe:[41076]",
"2": "pipe:[40056]",
"20": "pipe:[41076]",
"23": "pipe:[38554]",
"24": "pipe:[38554]",
"29": "pipe:[41077]",
"30": "pipe:[41077]",
+ "32": "/dev/ptmx",
"4": "pipe:[41046]",
"5": "pipe:[41046]",
"6": "pipe:[41047]",
"7": "pipe:[41047]",
}
❯ onExit tests/index.test.ts:117:34
❯ wrapper.ts:93:9
This error originated in "tests/index.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 "can be written to". 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:
tests/index.test.ts#L250
AssertionError: expected { '0': 'pipe:[40054]', …(19) } to strictly equal { '0': 'pipe:[40054]', …(18) }
- Expected
+ Received
Object {
"0": "pipe:[40054]",
"1": "pipe:[40055]",
"10": "pipe:[38545]",
"11": "pipe:[38545]",
"114": "pipe:[38214]",
"117": "pipe:[38215]",
"14": "pipe:[41048]",
"15": "pipe:[41048]",
"19": "pipe:[41076]",
"2": "pipe:[40056]",
"20": "pipe:[41076]",
"23": "pipe:[38554]",
"24": "pipe:[38554]",
"29": "pipe:[41077]",
"30": "pipe:[41077]",
+ "32": "/dev/ptmx",
"4": "pipe:[41046]",
"5": "pipe:[41046]",
"6": "pipe:[41047]",
"7": "pipe:[41047]",
}
❯ onExit tests/index.test.ts:250:34
❯ wrapper.ts:93:9
This error originated in "tests/index.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 "respects env". 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:
tests/index.test.ts#L466
AssertionError: expected { '0': 'pipe:[40054]', …(21) } to strictly equal { '0': 'pipe:[40054]', …(20) }
- Expected
+ Received
Object {
"0": "pipe:[40054]",
"1": "pipe:[40055]",
"10": "pipe:[38545]",
"11": "pipe:[38545]",
"114": "pipe:[38214]",
"117": "pipe:[38215]",
"14": "pipe:[41048]",
"15": "pipe:[41048]",
"19": "pipe:[41076]",
"2": "pipe:[40056]",
"20": "pipe:[41076]",
"23": "pipe:[38554]",
"24": "pipe:[38554]",
"29": "pipe:[41077]",
"30": "pipe:[41077]",
"32": "/dev/ptmx",
"35": "/dev/pts/0",
"4": "pipe:[41046]",
"5": "pipe:[41046]",
+ "54": "/dev/ptmx",
"6": "pipe:[41047]",
"7": "pipe:[41047]",
}
❯ tests/index.test.ts:466:34
This error originated in "tests/index.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 "can run concurrent shells". 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.
|
tests/index.test.ts > PTY > resize after exit shouldn't throw:
tests/index.test.ts#L271
AssertionError: expected [Function] to not throw an error but 'Error: ioctl TIOCSWINSZ failed: Bad f…' was thrown
- Expected:
undefined
+ Received:
"Error: ioctl TIOCSWINSZ failed: Bad file descriptor (os error 9)"
❯ onExit tests/index.test.ts:271:20
❯ wrapper.ts:93:9
|
Build and test on x86_64-unknown-linux-gnu
Process completed with exit code 1.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
bindings-aarch64-apple-darwin
Expired
|
230 KB |
|
bindings-x86_64-apple-darwin
Expired
|
239 KB |
|