Mitosheet default df renderer #3238
Annotations
2 errors, 3 warnings, and 1 notice
Start a server and run tests:
tests/jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts#L26
1) [chromium] › jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:14:7 › Mitosheet JupyterLab integration › Can run the generated code
Error: expect(received).toBe(expected) // Object.is equality
Expected: 3
Received: 2
24 | await page.notebook.setCell(2, 'code', `mitosheet.sheet(df)`);
25 | await page.notebook.runCell(2);
> 26 | await getNumberOfColumns(page, 2).then((num) => expect(num).toBe(3));
| ^
27 | });
28 |
29 |
at /home/runner/work/mito/mito/tests/jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:26:65
at /home/runner/work/mito/mito/tests/jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:26:5
|
Start a server and run tests:
tests/jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts#L126
2) [chromium] › jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:116:7 › Mitosheet JupyterLab integration › Automatically inserts new cell if user deletes mitosheet code
Error: Timed out 5000ms waiting for expect(locator).toHaveCount(expected)
Locator: locator('.jp-Notebook .jp-InputPrompt')
Expected: 1
Received: 2
Call log:
- expect.toHaveCount with timeout 5000ms
- waiting for locator('.jp-Notebook .jp-InputPrompt')
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
- locator resolved to 2 elements
- unexpected value "2"
124 | await page.locator('.jp-Notebook .jp-InputPrompt').nth(1).click();
125 | await page.keyboard.type('dd');
> 126 | await expect(page.locator('.jp-Notebook .jp-InputPrompt')).toHaveCount(1);
| ^
127 |
128 | // Make another edit and check that the modal doesn't appear, and that the cell below the mitosheet call has been updated
129 | await updateCellValue(page, 'new cell value', "'another cell value'");
at /home/runner/work/mito/mito/tests/jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:126:64
|
The following actions uses node12 which is deprecated and will be forced to run on node16: styfle/cancel-workflow-action@0.7.0, actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: styfle/cancel-workflow-action@0.7.0, actions/checkout@v2, actions/setup-python@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "test-results-grid-macos-latest-python3.10-firefox".
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/
|
Start a server and run tests
2 flaky
[chromium] › jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:14:7 › Mitosheet JupyterLab integration › Can run the generated code
[chromium] › jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:116:7 › Mitosheet JupyterLab integration › Automatically inserts new cell if user deletes mitosheet code
1 skipped
3 passed (1.1m)
|
Loading