Self-improve, Cowork pilotability & 1.0.0 GA audit hardening #42
Annotations
10 errors and 2 warnings
|
Run tests with coverage:
tests/hooks/user-hooks.test.ts#L199
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/hooks/user-hooks.test.ts:199:5
|
|
Run tests with coverage:
tests/features/cloud-lsp-ide.test.ts#L444
AssertionError: expected false to be true // Object.is equality
- Expected
+ Received
- true
+ false
❯ tests/features/cloud-lsp-ide.test.ts:444:20
|
|
Run tests with coverage:
tests/desktop-automation/native-providers.test.ts#L565
SyntaxError: Unexpected token 'export'
❯ tests/desktop-automation/native-providers.test.ts:565:45
Module SyntaxError: Unexpected token 'export' seems to be an ES Module but shipped in a CommonJS package. You might want to create an issue to the package "SyntaxError: Unexpected token 'export'" asking them to ship the file in .mjs extension or add "type": "module" in their package.json.
As a temporary workaround you can try to inline the package by updating your config:
// vitest.config.js
export default {
test: {
server: {
deps: {
inline: [
"SyntaxError: Unexpected token 'export'"
]
}
}
}
}
|
|
Run tests with coverage:
tests/commands/autonomous-code-command.test.ts#L5076
AssertionError: expected 'blocked' to be 'verified' // Object.is equality
Expected: "verified"
Received: "blocked"
❯ tests/commands/autonomous-code-command.test.ts:5076:27
|
|
Run tests with coverage:
tests/commands/autonomous-code-command.test.ts#L4910
AssertionError: expected 'blocked' to be 'verified' // Object.is equality
Expected: "verified"
Received: "blocked"
❯ tests/commands/autonomous-code-command.test.ts:4910:27
|
|
Run tests with coverage:
tests/commands/autonomous-code-command.test.ts#L4642
AssertionError: expected 'blocked' to be 'verified' // Object.is equality
Expected: "verified"
Received: "blocked"
❯ tests/commands/autonomous-code-command.test.ts:4642:27
|
|
Run tests with coverage:
tests/commands/autonomous-code-command.test.ts#L1579
AssertionError: expected 'blocked' to be 'verified' // Object.is equality
Expected: "verified"
Received: "blocked"
❯ tests/commands/autonomous-code-command.test.ts:1579:27
|
|
Run tests with coverage:
tests/commands/autonomous-code-command.test.ts#L1481
AssertionError: expected 'blocked' to be 'verified' // Object.is equality
Expected: "verified"
Received: "blocked"
❯ tests/commands/autonomous-code-command.test.ts:1481:27
|
|
Run tests with coverage:
tests/commands/autonomous-code-command.test.ts#L165
AssertionError: expected 'blocked' to be 'verified' // Object.is equality
Expected: "verified"
Received: "blocked"
❯ tests/commands/autonomous-code-command.test.ts:165:27
|
|
Run tests with coverage:
src/hooks/user-hooks.ts#L324
Error: write EPIPE
❯ src/hooks/user-hooks.ts:324:21
❯ UserHooksManager.executeCommand src/hooks/user-hooks.ts:296:12
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -32, code: 'EPIPE', syscall: 'write' }
This error originated in "tests/hooks/user-hooks.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 "runs handler when `if` matches tool name exactly". 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.
|
|
Complete job
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 will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Post Checkout repository
The process '/usr/bin/git' failed with exit code 128
|
background
wait
wait-all
cancel
Loading