Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - Local integration tests failing after upgrading the Jupyterlab extension for conda-store to 2024.11.1 #2908

Closed
marcelovilla opened this issue Jan 14, 2025 · 0 comments · Fixed by #2911

Comments

@marcelovilla
Copy link
Member

Describe the bug

After merging nebari-dev/nebari-docker-images#192, which upgrade the Jupyterlab extension for conda-store to 2024.11.1, our local integration tests are now failing with the following error:

FAILED test_playwright.py::test_conda_store_ui[navigator_session0-namespaces0] - AssertionError: Locator expected to be visible
Actual value: <element(s) not found> 
Call log:
  - LocatorAssertions.to_be_visible with timeout 5000ms
  -   - waiting for get_by_text("Create Environment")

The full traceback can be found at any of the failed runs, for example: https://github.com/nebari-dev/nebari/actions/runs/12708958029

As the error suggests, in the 2024.11.1 version of the Jupyterlab extension for conda-store, there is no Create Environment text anymore.

Screenshot for 2024.3.1:
image

Screenshot for 2024.11.1:
image

Expected behavior

The Jupyterlab extension for conda-store tests should pass

OS and architecture in which you are running Nebari

CI

How to Reproduce the problem?

Run the local integration tests against a deployment of Nebari using the Jupyterlab docker image with the main-72e4903-20250110 tag.

Command output

No response

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done 💪🏾
Development

Successfully merging a pull request may close this issue.

1 participant