Add realtime example #386
Annotations
11 errors and 2 warnings
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_frontend.py#L367
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 <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_frontend.py#L367
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 <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
- locator resolved to <span> Parcels</span>
- unexpected value "checked"
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L4
test_map
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L4
test_map
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L4
test_map
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L4
test_map
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L32
test_layer_control
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L32
test_layer_control
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L32
test_layer_control
RuntimeError: Runtime hasn't been created!
|
Test with pytest and retry flaky tests up to 3 times:
tests/test_package.py#L32
test_layer_control
RuntimeError: Runtime hasn't been created!
|
Run pre-commit/[email protected]
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.
|
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/
|
Loading