ale
02/06/2023, 1:44 PM../../../.pyenv/versions/3.10.9/envs/prefect-huggingface/lib/python3.10/site-packages/prefect/testing/standard_test_suites/task_runners.py:155
/Users/alessandro.lollo/.pyenv/versions/3.10.9/envs/prefect-huggingface/lib/python3.10/site-packages/prefect/testing/standard_test_suites/task_runners.py:155: PytestUnknownMarkWarning: Unknown pytest.mark.flaky - is this a typo? You can register custom marks to avoid this warning - for details, see <https://docs.pytest.org/en/stable/how-to/mark.html>
@pytest.mark.flaky(max_runs=4) # Threads do not consistently yield
Not sure whatโs the issue here, anyone experiencing this?
tests/test_tasks.py::test_get_inference_result_fails
/Users/alessandro.lollo/.pyenv/versions/3.10.9/envs/prefect-huggingface/lib/python3.10/site-packages/prefect/orion/database/migrations/versions/sqlite/2022_04_25_135207_b75d279ba985_replace_version_with_checksum.py:102: RemovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings. Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: <https://sqlalche.me/e/b8d9>)
meta_data = sa.MetaData(bind=connection)
tests/test_tasks.py::test_get_inference_result_fails
/Users/alessandro.lollo/.pyenv/versions/3.10.9/lib/python3.10/contextlib.py:142: SAWarning: Skipped unsupported reflection of expression-based index ix_flow_run__coalesce_start_time_expected_start_time_desc
next(self.gen)
tests/test_tasks.py::test_get_inference_result_fails
/Users/alessandro.lollo/.pyenv/versions/3.10.9/lib/python3.10/contextlib.py:142: SAWarning: Skipped unsupported reflection of expression-based index ix_flow_run__coalesce_start_time_expected_start_time_asc
next(self.gen)
-- Docs: <https://docs.pytest.org/en/stable/how-to/capture-warnings.html>
These seems to be related to SQLAlchemy 2.0.
However, in my environment I have
prefect==2.7.11
and
sqlalchemy==1.4.46
Anyone experiencing the same? Is this something I should be worried about? ๐
Anna Geller
Andrew Huang
02/06/2023, 7:06 PMZanie
ale
02/08/2023, 8:18 AM