Skip to content

vscode-insiders-release #837

vscode-insiders-release

vscode-insiders-release #837

Manually triggered December 6, 2024 13:23
Status Success
Total duration 18m 9s
Artifacts

vscode-insiders-release.yml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

1 error, 6 warnings, and 1 notice
command-custom.test.ts:45:3 › create a new user command via the custom commands menu: vscode/test/e2e/command-custom.test.ts#L92
1) command-custom.test.ts:45:3 › create a new user command via the custom commands menu ────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByText('New Custom Cody Command: Prompt') Expected: visible Received: <element(s) not found> Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByText('New Custom Cody Command: Prompt') 90 | // Enter prompt 91 | const promptInputTitle = page.getByText('New Custom Cody Command: Prompt') > 92 | await expect(promptInputTitle).toBeVisible() | ^ 93 | const promptInputBox = page.getByPlaceholder( 94 | 'e.g. Create five different test cases for the selected code' 95 | ) at /home/runner/work/cody/cody/vscode/test/e2e/command-custom.test.ts:92:36
release
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Slow Test: vscode/chat-atFile.test.ts#L1
vscode/chat-atFile.test.ts took 1.3m
Slow Test: vscode/chat-input.test.ts#L1
vscode/chat-input.test.ts took 58.4s
Slow Test: vscode/initial-context.test.ts#L1
vscode/initial-context.test.ts took 51.9s
Slow Test: vscode/command-edit.test.ts#L1
vscode/command-edit.test.ts took 44.8s
Slow Test: vscode/command-core.test.ts#L1
vscode/command-core.test.ts took 43.4s
🎭 Playwright Run Summary
1 flaky command-custom.test.ts:45:3 › create a new user command via the custom commands menu ─────────── 3 skipped 43 passed (11.3m)