Chat: Fix hanging issue in repository name resolution for workspaces … #128
Annotations
2 errors, 11 warnings, and 1 notice
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#L179
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" custom-hover="true" autocapitalize="off" aria-haspopup="menu" aria-expanded="true" aria-autocomplete="list" aria-controls="quickInput_list" aria-activedescendant="list_id_4_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
|
release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/create-release@v1, actions/upload-release-asset@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/create-release@v1, actions/upload-release-asset@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Slow Test:
vscode/chat-atFile.test.ts#L1
vscode/chat-atFile.test.ts took 1.1m
|
Slow Test:
vscode/command-custom.test.ts#L1
vscode/command-custom.test.ts took 56.3s
|
Slow Test:
vscode/chat-input.test.ts#L1
vscode/chat-input.test.ts took 45.6s
|
Slow Test:
vscode/initial-context.test.ts#L1
vscode/initial-context.test.ts took 39.3s
|
Slow Test:
vscode/command-edit.test.ts#L1
vscode/command-edit.test.ts took 35.4s
|
release
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/
|
release
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/
|
release
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/
|
release
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/
|
🎭 Playwright Run Summary
1 flaky
chat-keyboard-shortcuts.test.ts:35:5 › re-opening chat adds selection ──────────────────────────
3 skipped
42 passed (8.6m)
|