test_layer_control_dynamic_update[chromium] AssertionError: Locator expected not to be checked Actual value: True Call log: LocatorAssertions.not_to_be_checked with timeout 5000ms - waiting for frame_locator("iframe[title=\"streamlit_folium\\.st_folium\"]").get_by_text("Parcels") - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked" - locator resolved to Parcels - unexpected value "checked"

build (3.10): tests/test_frontend.py#L367

build (3.10): tests/test_package.py#L4

test_map RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L4

test_map RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L4

test_map RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L4

test_map RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L32

test_layer_control RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L32

test_layer_control RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L32

test_layer_control RuntimeError: Runtime hasn't been created!

build (3.10): tests/test_package.py#L32

test_layer_control RuntimeError: Runtime hasn't been created!

build (3.11)

The job was canceled because "_3_8" failed.

build (3.11): tests/test_frontend.py#L367

build (3.11)

The operation was canceled.

build (3.9)

The job was canceled because "_3_8" failed.

build (3.9): tests/test_frontend.py#L363

build (3.9)

The operation was canceled.

build (3.8)

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4, actions/setup-node@v3, pre-commit/[email protected], actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

build (3.8)

The following actions uses node12 which is deprecated and will be forced to run on node16: pre-commit/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

build (3.8)

There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/187/merge, Key: pre-commit-2-99d376b98fa405ec3c3f65294272a222bdecbc39fad06de4722f3eee969379bf-062e92ae6c567da07cdf5b8d93d27f29a020e56dc5b02b17aaa0f75fef4c1a76, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.

build (3.8)

No files were found with the provided path: screenshot*.png. No artifacts will be uploaded.

build (3.10)

There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/187/merge, Key: pre-commit-2-284c55692827fb478d095104d3dd2b46f9d56886aca889e70e967dd68d24dbe0-062e92ae6c567da07cdf5b8d93d27f29a020e56dc5b02b17aaa0f75fef4c1a76, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.

build (3.9)

There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/187/merge, Key: pre-commit-2-3833dd35c7297f8babf73ec0344893960f58d2136c8802f99288298dfa158e15-062e92ae6c567da07cdf5b8d93d27f29a020e56dc5b02b17aaa0f75fef4c1a76, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.

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: "screenshots". 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/

Artifacts

Produced during runtime

Name	Size
screenshots Expired	461 KB

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add realtime example #386

Summary

Add realtime example #386

Jobs

Run details

run_tests_each_PR.yml

Annotations

Artifacts