** Merge proposal linked: https://code.launchpad.net/~txiao/charm-sysconfig/+git/charm-sysconfig/+merge/428037
-- You received this bug notification because you are a member of Nagios Charm developers, which is subscribed to Nagios Charm. https://bugs.launchpad.net/bugs/1983398 Title: Update pytest fixture for async functions Status in charm-infra-node: Fix Committed Status in logrotate-charm: Fix Committed Status in Nagios Charm: Fix Committed Status in charm-sysconfig: In Progress Status in Thruk Agent Charm: Fix Committed Status in juju-autoreg: New Bug description: Starting from `pytest-asyncio`'s most recent release (version 0.19.0), strict mode is enforced by default [1], which requires the usage of `@pytest.mark.asyncio` and `@pytest_asyncio.fixture` [2]. Without these markers, tests and fixtures are not considered as asyncio- driven, resulting functional tests failures. For charms using pytest framework, we need to update their functional tests by replacing the current used `@pytest.fixture` with `@pytest_asyncio.fixture` in test files. [1]: https://github.com/pytest-dev/pytest-asyncio/issues/390 [2]: https://github.com/pytest-dev/pytest-asyncio#strict-mode To manage notifications about this bug go to: https://bugs.launchpad.net/charm-infra-node/+bug/1983398/+subscriptions -- Mailing list: https://launchpad.net/~nagios-charmers Post to : [email protected] Unsubscribe : https://launchpad.net/~nagios-charmers More help : https://help.launchpad.net/ListHelp
