Skip to content

feat(webview): add Upgrade to Pro & Enterprise plan to user menu #25311

feat(webview): add Upgrade to Pro & Enterprise plan to user menu

feat(webview): add Upgrade to Pro & Enterprise plan to user menu #25311

Triggered via pull request January 11, 2025 11:44
Status Failure
Total duration 7m 7s
Artifacts

ci.yml

on: pull_request
fast_tests_matrix_prep
0s
fast_tests_matrix_prep
slow_tests_matrix_prep
0s
slow_tests_matrix_prep
Matrix: test-integration
Matrix: test-unit
Matrix: test-e2e
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 28 warnings, and 5 notices
test-integration (ubuntu)
Process completed with exit code 1.
chat-keyboard-shortcuts.test.ts:35:5 › re-opening chat adds selection: vscode/test/e2e/chat-keyboard-shortcuts.test.ts#L1
1) chat-keyboard-shortcuts.test.ts:35:5 › re-opening chat adds selection ───────────────────────── Test timeout of 30000ms exceeded.
chat-keyboard-shortcuts.test.ts:35:5 › re-opening chat adds selection: vscode/test/e2e/common.ts#L198
1) chat-keyboard-shortcuts.test.ts:35:5 › re-opening chat adds selection ───────────────────────── Error: locator.fill: Target page, context or browser has been closed Call log: - waiting for getByPlaceholder('Type the name of a command to run.') - locator resolved to <input wrap="off" type="text" class="input" role="combobox" autocorrect="off" spellcheck="false" aria-label="input" autocapitalize="off" aria-haspopup="menu" aria-expanded="true" aria-autocomplete="list" aria-controls="quickInput_list" aria-activedescendant="list_id_5_0" aria-describedby="quickInput_message" placeholder="Type the name of a command to run."/> - fill("buzz.ts") - attempting fill action - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #1 - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #5 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #6 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #7 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #8 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #9 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #10 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #11 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #12 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #13 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #14 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #15 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #16 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #17 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #18 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #19 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fill action, attempt #20 - waiting 500ms - waiting for element to be visible, enabled and editable - element is not visible - retrying fil
fast_tests_matrix_prep
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
slow_tests_matrix_prep
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-integration (ubuntu)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-unit (ubuntu, 20)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-unit (ubuntu, 18)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test-e2e (ubuntu, 4/5)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Slow Test: vscode/command-edit.test.ts#L1
vscode/command-edit.test.ts took 48.1s
Slow Test: vscode/enterprise-cody-ignore.test.ts#L1
vscode/enterprise-cody-ignore.test.ts took 18.5s
test-e2e (ubuntu, 5/5)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Slow Test: vscode/initial-context.test.ts#L1
vscode/initial-context.test.ts took 54.3s
Slow Test: vscode/uninstall.test.ts#L1
vscode/uninstall.test.ts took 31.1s
Slow Test: vscode/support-menu-items.test.ts#L1
vscode/support-menu-items.test.ts took 21.6s
test-e2e (ubuntu, 1/5)
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.4m
Slow Test: vscode/auth.test.ts#L1
vscode/auth.test.ts took 34.2s
Slow Test: vscode/attribution.test.ts#L1
vscode/attribution.test.ts took 23.4s
test-e2e (ubuntu, 2/5)
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-input.test.ts#L1
vscode/chat-input.test.ts took 59.6s
Slow Test: vscode/chat-history.test.ts#L1
vscode/chat-history.test.ts took 22.8s
Slow Test: vscode/chat-messages.test.ts#L1
vscode/chat-messages.test.ts took 20.8s
Slow Test: vscode/chat-context.test.ts#L1
vscode/chat-context.test.ts took 15.7s
test-e2e (ubuntu, 3/5)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Slow Test: vscode/command-custom.test.ts#L1
vscode/command-custom.test.ts took 1.2m
Slow Test: vscode/command-core.test.ts#L1
vscode/command-core.test.ts took 45.0s
Slow Test: vscode/chat-rateLimit.test.ts#L1
vscode/chat-rateLimit.test.ts took 36.0s
Slow Test: vscode/code-actions.test.ts#L1
vscode/code-actions.test.ts took 35.8s
Slow Test: vscode/command-commit.test.ts#L1
vscode/command-commit.test.ts took 15.2s
🎭 Playwright Run Summary
1 skipped 6 passed (1.6m)
🎭 Playwright Run Summary
2 skipped 8 passed (2.1m)
🎭 Playwright Run Summary
2 skipped 10 passed (2.4m)
🎭 Playwright Run Summary
1 flaky chat-keyboard-shortcuts.test.ts:35:5 › re-opening chat adds selection ────────────────────────── 9 passed (3.1m)
🎭 Playwright Run Summary
13 passed (3.4m)