nagios-charmers team mailing list archive

[Tianqi Xiao <1983398@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Starting from `pytest-asyncio`'s most recent release (version 0.19.0),
strict mode is enforced by default, which requires the usage of
`@pytest.mark.asyncio` and `@pytest_asyncio.fixture`. 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.

** Affects: charm-advanced-routing
     Importance: Undecided
         Status: New

** Affects: charm-infra-node
     Importance: Undecided
     Assignee: Tianqi Xiao (txiao)
         Status: New

** Affects: charm-logrotated
     Importance: Undecided
         Status: New

** Affects: charm-nagios
     Importance: Undecided
         Status: New

** Affects: charm-sysconfig
     Importance: Undecided
         Status: New

** Affects: charm-thruk-agent
     Importance: Undecided
         Status: New

** Also affects: charm-sysconfig
   Importance: Undecided
       Status: New

** Also affects: charm-thruk-agent
   Importance: Undecided
       Status: New

** Also affects: charm-advanced-routing
   Importance: Undecided
       Status: New

** Also affects: charm-logrotated
   Importance: Undecided
       Status: New

** Also affects: charm-nagios
   Importance: Undecided
       Status: New

-- 
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-advanced-routing:
  New
Status in charm-infra-node:
  New
Status in logrotate-charm:
  New
Status in Nagios Charm:
  New
Status in charm-sysconfig:
  New
Status in Thruk Agent Charm:
  New

Bug description:
  Starting from `pytest-asyncio`'s most recent release (version 0.19.0),
  strict mode is enforced by default, which requires the usage of
  `@pytest.mark.asyncio` and `@pytest_asyncio.fixture`. 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-advanced-routing/+bug/1983398/+subscriptions