Add drive handling operations #362
DenisaCGbuild.yml
on: pull_request
build
3m 13s
Check Links
41s
Annotations
3 errors, 5 warnings, and 1 notice
|
tests/jupyter_drives.spec.ts:9:5 › should emit an activation console message:
ui-tests/tests/jupyter_drives.spec.ts#L1
1) tests/jupyter_drives.spec.ts:9:5 › should emit an activation console message ──────────────────
Test timeout of 60000ms exceeded.
|
|
tests/jupyter_drives.spec.ts:9:5 › should emit an activation console message:
ui-tests/tests/jupyter_drives.spec.ts#L16
1) tests/jupyter_drives.spec.ts:9:5 › should emit an activation console message ──────────────────
Error: locator.click: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByRole('main').getByRole('tab', { name: 'Launcher' })
- locator resolved to <li title="" role="tab" tabindex="0" id="tab-key-2-0" aria-selected="true" data-id="launcher-0" class="lm-TabBar-tab jp-mod-current lm-mod-current">…</li>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <dialog aria-modal="true" class="lm-Widget jp-Dialog jp-ThemedContainer" aria-label="Directory not found Directory not found: "s3:"">…</dialog> intercepts pointer events
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <dialog aria-modal="true" class="lm-Widget jp-Dialog jp-ThemedContainer" aria-label="Directory not found Directory not found: "s3:"">…</dialog> intercepts pointer events
- retrying click action
- waiting 100ms
112 × waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <dialog aria-modal="true" class="lm-Widget jp-Dialog jp-ThemedContainer" aria-label="Directory not found Directory not found: "s3:"">…</dialog> intercepts pointer events
- retrying click action
- waiting 500ms
14 | });
15 |
> 16 | await page.goto();
| ^
17 |
18 | expect(
19 | logs.filter(
at ActivityHelper.activateTab (/home/runner/work/jupyter-drives/jupyter-drives/ui-tests/node_modules/@jupyterlab/galata/src/helpers/activity.ts:192:17)
at Proxy.waitIsReady (/home/runner/work/jupyter-drives/jupyter-drives/ui-tests/node_modules/@jupyterlab/galata/src/fixtures.ts:358:9)
at Proxy.goto (/home/runner/work/jupyter-drives/jupyter-drives/ui-tests/node_modules/@jupyterlab/galata/src/jupyterlabpage.ts:502:5)
at /home/runner/work/jupyter-drives/jupyter-drives/ui-tests/tests/jupyter_drives.spec.ts:16:3
|
|
Integration tests
Process completed with exit code 1.
|
|
build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check Links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test_isolated
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Integration tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "extension-artifacts", "jupyter_drives-playwright-tests".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
🎭 Playwright Run Summary
1 failed
tests/jupyter_drives.spec.ts:9:5 › should emit an activation console message ───────────────────
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
extension-artifacts
|
213 KB |
|
|
jupyter_drives-playwright-tests
|
3.19 MB |
|