patch: workaround pytest-asyncio issue #186
Conversation
|
tested on canonical/mysql-k8s-operator#429 |
There was a problem hiding this comment.
This assertion is important to properly parallelize runners
IMO, this should be fixed by pinning pytest-asyncio, or by fixing a misconfigured pytest-asyncio
I don't think data-platform-workflows should carry a workaround for markers getting duplicated
Duplicated markers may also affect test parameterization and Allure
It's an economy argument - this will eventually show up on many other repos while the bug is not fixed on upstream, doing centrally would make it easier to mange. |
|
I don't think the issue is pytest-asyncio, I think the issue is with our configuration and/or pytest-operator |
|
Closed in favor of canonical/mysql-k8s-operator#430 |
Issue
pytest-asyncio 0.27.3 is duplication function markers, breaking tests group collection, that are asserting for one group marker per test.
This could be also be fixed by pinning pytest-asyncio to ^0.21.1 on charms, but IMO it's better suited do it here, since avoid pinning on multiple repositories.