all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    debian-bookworm:
      ansible_connection: ssh
      ansible_host: 2a13:1a81:8000:3124:f816:3eff:fe79:e57e
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: nova
        cloud: regiocloud-a-ci
        external_id: 3322295a-37b0-44da-90bd-256a66ad055c
        host_id: 0d3d02185f810c959252bd1d303ec55040bf5bb0b401cceef814c3a7
        interface_ip: 2a13:1a81:8000:3124:f816:3eff:fe79:e57e
        label: debian-bookworm
        node_properties: {}
        private_ipv4: 10.128.7.244
        private_ipv6: null
        provider: regiocloud-a
        public_ipv4: 81.163.192.159
        public_ipv6: 2a13:1a81:8000:3124:f816:3eff:fe79:e57e
        region: null
        slot: null
  vars:
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-config/zuul.d/jobs.yaml@main#2>'
      - '<Job python-black explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-jobs/.zuul.yaml@main#54>'
      - '<Job python-black explicit: None implied: None source: osism/ansible-collection-commons/.zuul.yaml@main#410>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: 139e81f2aeb547108c8ffd7ab4711dad
      build_refs:
      - branch: main
        change: '854'
        change_message: "chore(deps): update dependency pytest to v9.1.0\n\nThis PR
          contains the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
          [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
          | `==9.0.3` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true)
          |\n\n---\n\n### Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
          [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
          pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
          changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/14533):
          When using `--doctest-modules`, autouse fixtures with `module`, `package`
          or `session` scope that are defined inline in Python test modules (not plugins
          or conftests) will now possibly execute twice.\n\n  If this is undesirable,
          move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
          explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
          pytest possibly collects Python modules twice, once as `pytest.Module` and
          once as a `DoctestModule` (depending on the configuration).\n  Due to improvements
          in pytest's fixture implementation, if e.g. the `DoctestModule` collects
          a fixture, it is now visible to it only, and not to the `Module`.\n  This
          means that both need to register the fixtures independently.\n\n##### Deprecations
          (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/10819):
          Added a deprecation warning for class-scoped fixtures defined as instance
          methods (without `@classmethod`). Such fixtures set attributes on a different
          instance than the test methods use, leading to unexpected behavior. Use
          `@classmethod` decorator instead -- by `yastcher`.\n\n  See `10819` and
          `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/12882):
          Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>`
          during teardown to request a fixture that was not already requested is now
          deprecated and will become an error in pytest 10.\n\n  See `dynamic-fixture-request-during-teardown`
          for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/13409):
          Using non-`~collections.abc.Collection` iterables (such as generators, iterators,
          or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize
          <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>`
          is now deprecated.\n\n  These iterables get exhausted after the first iteration,\n
          \ leading to tests getting unexpectedly skipped in cases such as running
          `pytest.main()` multiple times,\n  using class-level parametrize decorators,\n
          \ or collecting tests multiple times.\n\n  See `parametrize-iterators` for
          details and suggestions.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
          <pytest.Config.getini>` to access configuration values instead.\n\n  See
          `config-inicfg` for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture
          registration APIs is now deprecated. These are internal pytest APIs that
          are used by some plugins.\n\n  Use the `node` parameter instead for fixture
          scoping. This enables more robust node-based\n  matching instead of string
          prefix matching.\n  If you've used `nodeid=None`, pass `node=session` instead.\n\n
          \ This will be removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
          The method of configuring hooks using markers, deprecated since pytest 7.2,
          is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
          details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
          The `--pastebin` option is now deprecated.\n  The same functionality is
          now available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
          for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The private `FixtureDef.has_location` attribute is now deprecated and will
          be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for
          details.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
          \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
          New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
          Added `pytest.register_fixture()` to register fixtures using an imperative
          interface.\n\n  This is an advanced function intended for use by plugins.\n\n
          \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
          <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
          during the collection phase and registers them automatically.\n  For some
          plugin usecases the declarative interface can be cumbersome or unviable,
          in which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
          Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
          [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/14371):
          Added `--max-warnings` command-line option and `max_warnings` configuration
          option to fail the test run when the number of warnings exceeds a given
          threshold -- by `miketheman`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
          Added the `assertion_text_diff_style` configuration option, allowing\n  string
          equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
          instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/8395):
          Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons
          with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta`
          is required and relative tolerance is not supported for datetime comparisons
          -- by `hamza-mobeen`.\n\n##### Improvements in existing functionality\n\n-
          [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/11225):
          `pytest.warns` now shows \"Regex pattern did not match\" instead of \"DID
          NOT WARN\" when warnings were emitted but the `match` pattern did not match.\n\n-
          [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
          Improved output of `--fixtures-per-test` by excluding internal-implementation
          fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/13241):
          `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec`
          for the type hint to the (old and not recommended) callable overload, instead
          of `Any`. This allows type checkers to raise errors when passing incorrect
          function parameters.\n  `func` can now also be passed as a kwarg, which
          the type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
          Improved the readability of \"DID NOT RAISE\" error messages by using the
          exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
          [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
          Added test coverage for compiled regex patterns in `pytest.raises` match
          parameter.\n\n- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
          <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow
          using it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
          Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
          decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
          in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
          Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/14430):
          When using `--setup-show`, a space is now printed after the test name (and
          possibly used fixtures), to separate it from the test result.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/14441):
          Reduced the default number of `gc.collect()` passes in the `unraisableexception`
          plugin from 5 to 1 on CPython, where reference counting makes a single pass
          sufficient. PyPy retains 5 passes due to object resurrection via `__del__`.
          This can noticeably speed up test suites that trigger many pytester runs.\n\n-
          [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
          Improved assertion failure explanations for equality comparisons between
          mapping objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The order in which fixture definitions overriding each other are resolved
          is now determined first by their *visibility* in the collection tree rather
          than by the order in which they are registered.\n\n  A fixture defined for
          a more specific node (e.g. a module or an item) now always takes precedence
          over one with the same name defined for a more general node (e.g. the session),
          even when the more general one was registered later.\n  Fixtures with non-comparable
          visibility or the same visibility keep the existing behavior of \"last registered
          wins\".\n  This change is supposed to only affect plugins which register
          multiple fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
          Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          Improved argparse program name to show `pytest`, `python -m pytest`, or
          `pytest.main()` based on how pytest was invoked, making help and error messages
          clearer.\n\n- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
          Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
          `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
          this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
          pytest issues a helpful warning and continues collecting the module normally.\n\n#####
          Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
          Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
          meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
          [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
          Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
          [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
          Fixed function-scoped fixture values being kept alive after a test was interrupted
          by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be
          released more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
          Fixed `capteesys` producing doubled output when used with `--capture=no`
          (`-s`).\n\n- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
          Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
          the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
          Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
          being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
          Fixed autouse fixtures defined inside a `unittest.TestCase` class running
          even when the class is decorated with `unittest.skip` or `unittest.skipIf`
          -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
          `unittest.SkipTest` is no longer considered an interactive exception, i.e.
          `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
          Fixed subtests running with `pytest-xdist` when their contexts contain objects
          that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
          [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Fixed conftest.py fixture scoping when `testpaths` points outside of the
          `rootdir <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files
          would incorrectly leak to sibling directories\n  when using a relative `testpaths`
          like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
          <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
          [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
          Display dictionary differences in assertion failures using the original
          key insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
          fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
          methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
          An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
          from being torn down, causing additional errors in the following tests.\n\n-
          [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
          Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
          entry on the undo stack when the underlying `setattr()` call fails (e.g.
          on immutable targets), causing an `AttributeError` crash during teardown.\n\n-
          [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
          Fixed `-v` hint in `pytest.raises` match diff not working because assertion
          verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
          Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
          <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
          Fixed direct parametrization causing the static fixture closure (as reflected
          in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit
          fixtures that are requested transitively from overridden fixtures.\n\n-
          [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
          Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
          before pytest tears down the warning filters installed for the session.
          Previously the collection ran from a cleanup callback whose order relative
          to other plugins' cleanups was not guaranteed, so an active `error` filter
          could be removed before the exception surfaced and a late resource leak
          would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
          now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
          [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
          Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
          when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
          [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
          Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
          [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
          Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
          the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
          [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
          Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
          detection, causing the regex diff display to be shown in some instances
          when the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
          Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
          specified through `addopts` were silently ignored.\n\n  Note that when targeting
          pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
          `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
          Fixed `pytest.approx` not recognizing types with `__array_interface__` as
          numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
          Fixed a regression where `-k` and `-m` expressions containing both backslash
          characters in identifiers and string literal arguments would incorrectly
          raise a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
          Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
          plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
          [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
          Fixed `Code.getargs()` incorrectly including local variable names in the
          returned argument tuple for functions with `*args` and/or `**kwargs`. The
          method was using `co_flags` bitmask values (`4` and `8`) directly as counts
          instead of converting them to `1` via `bool()`, and was not accounting for
          `co_kwonlyargcount` when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
          Logging capture now works for non-propagating loggers.\n  Previously only
          logs which reached the root logger were captured.\n  This includes `caplog`
          and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
          Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
          now always matches the number of `<testcase>` elements in the file. In some
          cases (test passes but fails during teardown) the `tests` attribute would
          report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
          `pytest_fixture_post_finalizer` is no longer called extra times for the
          same fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
          Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
          single-element tuple values when using a string argnames with a trailing
          comma (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves
          like the tuple form `(\"arg\",)`, treating argvalues as a list of tuples
          to unpack.\n\n##### Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
          Document safer alternatives and scope guidance for monkeypatching standard
          library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
          Document that `@pytest.hookimpl(specname=...)` only works for function names
          starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
          Document that doctests do not support parametrized fixtures, including parametrized
          autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
          Clarified how the `request` fixture provides indirect parametrization values
          via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
          Clarified in the documentation that hook implementations defined in `conftest.py`
          files are not available to other plugins during their `pytest_addoption()`
          execution, as conftest files are discovered and loaded after builtin and
          third-party plugins have been initialized. However, initial conftest files
          themselves can implement `pytest_addoption()` to add their own command-line
          options.\n- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
          Clarified how subtest progress markers are shown in the documentation.\n-
          [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
          The `ini options ref` section of the API Reference now specified the type
          and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
          Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
          plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
          The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
          Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
          at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
          Pointing at a tag keeps the example in sync with the version users actually
          install, while remaining stable when the project's main branch moves on.\n\n#####
          Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
          Improved the recursion traceback test to exercise all requested traceback
          styles.\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
          (UTC)\n\n- Branch creation\n  - At any time (no schedule defined)\n- Automerge\n
          \ - At any time (no schedule defined)\n\n\U0001F6A6 **Automerge**: Disabled
          by config. Please merge this manually once you are satisfied.\n\n\u267B
          **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry
          checkbox.\n\n\U0001F515 **Ignore**: Close this PR and you won't be reminded
          about this update again.\n\n---\n\n - [ ] <!-- rebase-check -->If you want
          to rebase/retry this PR, check this box\n\n---\n\nThis PR was generated
          by [Mend Renovate](https://mend.io/renovate/). View the [repository job
          log](https://developer.mend.io/github/osism/ansible-collection-commons).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
        change_url: https://github.com/osism/ansible-collection-commons/pull/854
        commit_id: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
        patchset: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-commons
          name: osism/ansible-collection-commons
          short_name: ansible-collection-commons
        src_dir: src/github.com/osism/ansible-collection-commons
        topic: null
      buildset: 0ddd81605f2f41169bf3bb2dda538c58
      buildset_refs:
      - branch: main
        change: '854'
        change_message: "chore(deps): update dependency pytest to v9.1.0\n\nThis PR
          contains the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
          [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
          | `==9.0.3` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true)
          |\n\n---\n\n### Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
          [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
          pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
          changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/14533):
          When using `--doctest-modules`, autouse fixtures with `module`, `package`
          or `session` scope that are defined inline in Python test modules (not plugins
          or conftests) will now possibly execute twice.\n\n  If this is undesirable,
          move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
          explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
          pytest possibly collects Python modules twice, once as `pytest.Module` and
          once as a `DoctestModule` (depending on the configuration).\n  Due to improvements
          in pytest's fixture implementation, if e.g. the `DoctestModule` collects
          a fixture, it is now visible to it only, and not to the `Module`.\n  This
          means that both need to register the fixtures independently.\n\n##### Deprecations
          (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/10819):
          Added a deprecation warning for class-scoped fixtures defined as instance
          methods (without `@classmethod`). Such fixtures set attributes on a different
          instance than the test methods use, leading to unexpected behavior. Use
          `@classmethod` decorator instead -- by `yastcher`.\n\n  See `10819` and
          `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/12882):
          Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>`
          during teardown to request a fixture that was not already requested is now
          deprecated and will become an error in pytest 10.\n\n  See `dynamic-fixture-request-during-teardown`
          for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/13409):
          Using non-`~collections.abc.Collection` iterables (such as generators, iterators,
          or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize
          <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>`
          is now deprecated.\n\n  These iterables get exhausted after the first iteration,\n
          \ leading to tests getting unexpectedly skipped in cases such as running
          `pytest.main()` multiple times,\n  using class-level parametrize decorators,\n
          \ or collecting tests multiple times.\n\n  See `parametrize-iterators` for
          details and suggestions.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
          <pytest.Config.getini>` to access configuration values instead.\n\n  See
          `config-inicfg` for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture
          registration APIs is now deprecated. These are internal pytest APIs that
          are used by some plugins.\n\n  Use the `node` parameter instead for fixture
          scoping. This enables more robust node-based\n  matching instead of string
          prefix matching.\n  If you've used `nodeid=None`, pass `node=session` instead.\n\n
          \ This will be removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
          The method of configuring hooks using markers, deprecated since pytest 7.2,
          is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
          details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
          The `--pastebin` option is now deprecated.\n  The same functionality is
          now available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
          for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The private `FixtureDef.has_location` attribute is now deprecated and will
          be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for
          details.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
          \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
          New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
          Added `pytest.register_fixture()` to register fixtures using an imperative
          interface.\n\n  This is an advanced function intended for use by plugins.\n\n
          \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
          <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
          during the collection phase and registers them automatically.\n  For some
          plugin usecases the declarative interface can be cumbersome or unviable,
          in which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
          Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
          [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/14371):
          Added `--max-warnings` command-line option and `max_warnings` configuration
          option to fail the test run when the number of warnings exceeds a given
          threshold -- by `miketheman`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
          Added the `assertion_text_diff_style` configuration option, allowing\n  string
          equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
          instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/8395):
          Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons
          with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta`
          is required and relative tolerance is not supported for datetime comparisons
          -- by `hamza-mobeen`.\n\n##### Improvements in existing functionality\n\n-
          [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/11225):
          `pytest.warns` now shows \"Regex pattern did not match\" instead of \"DID
          NOT WARN\" when warnings were emitted but the `match` pattern did not match.\n\n-
          [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
          Improved output of `--fixtures-per-test` by excluding internal-implementation
          fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/13241):
          `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec`
          for the type hint to the (old and not recommended) callable overload, instead
          of `Any`. This allows type checkers to raise errors when passing incorrect
          function parameters.\n  `func` can now also be passed as a kwarg, which
          the type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
          Improved the readability of \"DID NOT RAISE\" error messages by using the
          exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
          [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
          Added test coverage for compiled regex patterns in `pytest.raises` match
          parameter.\n\n- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
          <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow
          using it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
          Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
          decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
          in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
          Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/14430):
          When using `--setup-show`, a space is now printed after the test name (and
          possibly used fixtures), to separate it from the test result.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/14441):
          Reduced the default number of `gc.collect()` passes in the `unraisableexception`
          plugin from 5 to 1 on CPython, where reference counting makes a single pass
          sufficient. PyPy retains 5 passes due to object resurrection via `__del__`.
          This can noticeably speed up test suites that trigger many pytester runs.\n\n-
          [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
          Improved assertion failure explanations for equality comparisons between
          mapping objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The order in which fixture definitions overriding each other are resolved
          is now determined first by their *visibility* in the collection tree rather
          than by the order in which they are registered.\n\n  A fixture defined for
          a more specific node (e.g. a module or an item) now always takes precedence
          over one with the same name defined for a more general node (e.g. the session),
          even when the more general one was registered later.\n  Fixtures with non-comparable
          visibility or the same visibility keep the existing behavior of \"last registered
          wins\".\n  This change is supposed to only affect plugins which register
          multiple fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
          Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          Improved argparse program name to show `pytest`, `python -m pytest`, or
          `pytest.main()` based on how pytest was invoked, making help and error messages
          clearer.\n\n- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
          Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
          `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
          this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
          pytest issues a helpful warning and continues collecting the module normally.\n\n#####
          Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
          Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
          meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
          [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
          Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
          [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
          Fixed function-scoped fixture values being kept alive after a test was interrupted
          by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be
          released more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
          Fixed `capteesys` producing doubled output when used with `--capture=no`
          (`-s`).\n\n- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
          Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
          the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
          Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
          being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
          Fixed autouse fixtures defined inside a `unittest.TestCase` class running
          even when the class is decorated with `unittest.skip` or `unittest.skipIf`
          -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
          `unittest.SkipTest` is no longer considered an interactive exception, i.e.
          `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
          Fixed subtests running with `pytest-xdist` when their contexts contain objects
          that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
          [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Fixed conftest.py fixture scoping when `testpaths` points outside of the
          `rootdir <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files
          would incorrectly leak to sibling directories\n  when using a relative `testpaths`
          like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
          <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
          [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
          Display dictionary differences in assertion failures using the original
          key insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
          fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
          methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
          An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
          from being torn down, causing additional errors in the following tests.\n\n-
          [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
          Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
          entry on the undo stack when the underlying `setattr()` call fails (e.g.
          on immutable targets), causing an `AttributeError` crash during teardown.\n\n-
          [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
          Fixed `-v` hint in `pytest.raises` match diff not working because assertion
          verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
          Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
          <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
          Fixed direct parametrization causing the static fixture closure (as reflected
          in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit
          fixtures that are requested transitively from overridden fixtures.\n\n-
          [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
          Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
          before pytest tears down the warning filters installed for the session.
          Previously the collection ran from a cleanup callback whose order relative
          to other plugins' cleanups was not guaranteed, so an active `error` filter
          could be removed before the exception surfaced and a late resource leak
          would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
          now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
          [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
          Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
          when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
          [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
          Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
          [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
          Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
          the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
          [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
          Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
          detection, causing the regex diff display to be shown in some instances
          when the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
          Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
          specified through `addopts` were silently ignored.\n\n  Note that when targeting
          pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
          `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
          Fixed `pytest.approx` not recognizing types with `__array_interface__` as
          numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
          Fixed a regression where `-k` and `-m` expressions containing both backslash
          characters in identifiers and string literal arguments would incorrectly
          raise a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
          Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
          plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
          [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
          Fixed `Code.getargs()` incorrectly including local variable names in the
          returned argument tuple for functions with `*args` and/or `**kwargs`. The
          method was using `co_flags` bitmask values (`4` and `8`) directly as counts
          instead of converting them to `1` via `bool()`, and was not accounting for
          `co_kwonlyargcount` when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
          Logging capture now works for non-propagating loggers.\n  Previously only
          logs which reached the root logger were captured.\n  This includes `caplog`
          and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
          Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
          now always matches the number of `<testcase>` elements in the file. In some
          cases (test passes but fails during teardown) the `tests` attribute would
          report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
          `pytest_fixture_post_finalizer` is no longer called extra times for the
          same fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
          Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
          single-element tuple values when using a string argnames with a trailing
          comma (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves
          like the tuple form `(\"arg\",)`, treating argvalues as a list of tuples
          to unpack.\n\n##### Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
          Document safer alternatives and scope guidance for monkeypatching standard
          library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
          Document that `@pytest.hookimpl(specname=...)` only works for function names
          starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
          Document that doctests do not support parametrized fixtures, including parametrized
          autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
          Clarified how the `request` fixture provides indirect parametrization values
          via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
          Clarified in the documentation that hook implementations defined in `conftest.py`
          files are not available to other plugins during their `pytest_addoption()`
          execution, as conftest files are discovered and loaded after builtin and
          third-party plugins have been initialized. However, initial conftest files
          themselves can implement `pytest_addoption()` to add their own command-line
          options.\n- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
          Clarified how subtest progress markers are shown in the documentation.\n-
          [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
          The `ini options ref` section of the API Reference now specified the type
          and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
          Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
          plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
          The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
          Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
          at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
          Pointing at a tag keeps the example in sync with the version users actually
          install, while remaining stable when the project's main branch moves on.\n\n#####
          Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
          Improved the recursion traceback test to exercise all requested traceback
          styles.\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
          (UTC)\n\n- Branch creation\n  - At any time (no schedule defined)\n- Automerge\n
          \ - At any time (no schedule defined)\n\n\U0001F6A6 **Automerge**: Disabled
          by config. Please merge this manually once you are satisfied.\n\n\u267B
          **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry
          checkbox.\n\n\U0001F515 **Ignore**: Close this PR and you won't be reminded
          about this update again.\n\n---\n\n - [ ] <!-- rebase-check -->If you want
          to rebase/retry this PR, check this box\n\n---\n\nThis PR was generated
          by [Mend Renovate](https://mend.io/renovate/). View the [repository job
          log](https://developer.mend.io/github/osism/ansible-collection-commons).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
        change_url: https://github.com/osism/ansible-collection-commons/pull/854
        commit_id: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
        patchset: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-commons
          name: osism/ansible-collection-commons
          short_name: ansible-collection-commons
        src_dir: src/github.com/osism/ansible-collection-commons
        topic: null
      change: '854'
      change_message: "chore(deps): update dependency pytest to v9.1.0\n\nThis PR
        contains the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
        | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
        [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
        | `==9.0.3` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true)
        |\n\n---\n\n### Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
        [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
        Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
        pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
        changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/14533):
        When using `--doctest-modules`, autouse fixtures with `module`, `package`
        or `session` scope that are defined inline in Python test modules (not plugins
        or conftests) will now possibly execute twice.\n\n  If this is undesirable,
        move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
        explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
        pytest possibly collects Python modules twice, once as `pytest.Module` and
        once as a `DoctestModule` (depending on the configuration).\n  Due to improvements
        in pytest's fixture implementation, if e.g. the `DoctestModule` collects a
        fixture, it is now visible to it only, and not to the `Module`.\n  This means
        that both need to register the fixtures independently.\n\n##### Deprecations
        (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/10819):
        Added a deprecation warning for class-scoped fixtures defined as instance
        methods (without `@classmethod`). Such fixtures set attributes on a different
        instance than the test methods use, leading to unexpected behavior. Use `@classmethod`
        decorator instead -- by `yastcher`.\n\n  See `10819` and `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/12882):
        Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>`
        during teardown to request a fixture that was not already requested is now
        deprecated and will become an error in pytest 10.\n\n  See `dynamic-fixture-request-during-teardown`
        for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/13409):
        Using non-`~collections.abc.Collection` iterables (such as generators, iterators,
        or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize
        <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>`
        is now deprecated.\n\n  These iterables get exhausted after the first iteration,\n
        \ leading to tests getting unexpectedly skipped in cases such as running `pytest.main()`
        multiple times,\n  using class-level parametrize decorators,\n  or collecting
        tests multiple times.\n\n  See `parametrize-iterators` for details and suggestions.\n\n-
        [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
        The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
        <pytest.Config.getini>` to access configuration values instead.\n\n  See `config-inicfg`
        for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
        Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration
        APIs is now deprecated. These are internal pytest APIs that are used by some
        plugins.\n\n  Use the `node` parameter instead for fixture scoping. This enables
        more robust node-based\n  matching instead of string prefix matching.\n  If
        you've used `nodeid=None`, pass `node=session` instead.\n\n  This will be
        removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
        The method of configuring hooks using markers, deprecated since pytest 7.2,
        is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
        details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
        The `--pastebin` option is now deprecated.\n  The same functionality is now
        available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
        for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
        The private `FixtureDef.has_location` attribute is now deprecated and will
        be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for details.\n\n-
        [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
        `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
        \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
        New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
        Added `pytest.register_fixture()` to register fixtures using an imperative
        interface.\n\n  This is an advanced function intended for use by plugins.\n\n
        \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
        <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
        during the collection phase and registers them automatically.\n  For some
        plugin usecases the declarative interface can be cumbersome or unviable, in
        which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
        Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
        [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/14371):
        Added `--max-warnings` command-line option and `max_warnings` configuration
        option to fail the test run when the number of warnings exceeds a given threshold
        -- by `miketheman`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
        Added the `assertion_text_diff_style` configuration option, allowing\n  string
        equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
        instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/8395):
        Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons
        with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta`
        is required and relative tolerance is not supported for datetime comparisons
        -- by `hamza-mobeen`.\n\n##### Improvements in existing functionality\n\n-
        [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/11225):
        `pytest.warns` now shows \"Regex pattern did not match\" instead of \"DID
        NOT WARN\" when warnings were emitted but the `match` pattern did not match.\n\n-
        [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
        Improved output of `--fixtures-per-test` by excluding internal-implementation
        fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/13241):
        `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec`
        for the type hint to the (old and not recommended) callable overload, instead
        of `Any`. This allows type checkers to raise errors when passing incorrect
        function parameters.\n  `func` can now also be passed as a kwarg, which the
        type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
        Improved the readability of \"DID NOT RAISE\" error messages by using the
        exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
        [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
        Added test coverage for compiled regex patterns in `pytest.raises` match parameter.\n\n-
        [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
        <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow using
        it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
        Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
        decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
        in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
        Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/14430):
        When using `--setup-show`, a space is now printed after the test name (and
        possibly used fixtures), to separate it from the test result.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/14441):
        Reduced the default number of `gc.collect()` passes in the `unraisableexception`
        plugin from 5 to 1 on CPython, where reference counting makes a single pass
        sufficient. PyPy retains 5 passes due to object resurrection via `__del__`.
        This can noticeably speed up test suites that trigger many pytester runs.\n\n-
        [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
        Improved assertion failure explanations for equality comparisons between mapping
        objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
        The order in which fixture definitions overriding each other are resolved
        is now determined first by their *visibility* in the collection tree rather
        than by the order in which they are registered.\n\n  A fixture defined for
        a more specific node (e.g. a module or an item) now always takes precedence
        over one with the same name defined for a more general node (e.g. the session),
        even when the more general one was registered later.\n  Fixtures with non-comparable
        visibility or the same visibility keep the existing behavior of \"last registered
        wins\".\n  This change is supposed to only affect plugins which register multiple
        fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
        Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
        Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()`
        based on how pytest was invoked, making help and error messages clearer.\n\n-
        [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
        Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
        `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
        this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
        pytest issues a helpful warning and continues collecting the module normally.\n\n#####
        Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
        Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
        meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
        [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
        Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
        [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
        Fixed function-scoped fixture values being kept alive after a test was interrupted
        by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be released
        more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
        Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`).\n\n-
        [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
        Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
        the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
        Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
        being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
        Fixed autouse fixtures defined inside a `unittest.TestCase` class running
        even when the class is decorated with `unittest.skip` or `unittest.skipIf`
        -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
        `unittest.SkipTest` is no longer considered an interactive exception, i.e.
        `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
        Fixed subtests running with `pytest-xdist` when their contexts contain objects
        that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
        [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
        Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir
        <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files would
        incorrectly leak to sibling directories\n  when using a relative `testpaths`
        like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
        <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
        [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
        Display dictionary differences in assertion failures using the original key
        insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
        fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
        methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
        An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
        from being torn down, causing additional errors in the following tests.\n\n-
        [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
        Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
        entry on the undo stack when the underlying `setattr()` call fails (e.g. on
        immutable targets), causing an `AttributeError` crash during teardown.\n\n-
        [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
        Fixed `-v` hint in `pytest.raises` match diff not working because assertion
        verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
        Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
        <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
        Fixed direct parametrization causing the static fixture closure (as reflected
        in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures
        that are requested transitively from overridden fixtures.\n\n- [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
        Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
        before pytest tears down the warning filters installed for the session. Previously
        the collection ran from a cleanup callback whose order relative to other plugins'
        cleanups was not guaranteed, so an active `error` filter could be removed
        before the exception surfaced and a late resource leak would pass silently.
        A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
        now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
        [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
        Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
        when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
        [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
        Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
        [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
        Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
        the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
        [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
        Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
        detection, causing the regex diff display to be shown in some instances when
        the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
        Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
        specified through `addopts` were silently ignored.\n\n  Note that when targeting
        pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
        `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
        Fixed `pytest.approx` not recognizing types with `__array_interface__` as
        numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
        Fixed a regression where `-k` and `-m` expressions containing both backslash
        characters in identifiers and string literal arguments would incorrectly raise
        a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
        Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
        plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
        [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
        Fixed `Code.getargs()` incorrectly including local variable names in the returned
        argument tuple for functions with `*args` and/or `**kwargs`. The method was
        using `co_flags` bitmask values (`4` and `8`) directly as counts instead of
        converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount`
        when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
        Logging capture now works for non-propagating loggers.\n  Previously only
        logs which reached the root logger were captured.\n  This includes `caplog`
        and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
        Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
        now always matches the number of `<testcase>` elements in the file. In some
        cases (test passes but fails during teardown) the `tests` attribute would
        report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
        `pytest_fixture_post_finalizer` is no longer called extra times for the same
        fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
        Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
        single-element tuple values when using a string argnames with a trailing comma
        (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves like
        the tuple form `(\"arg\",)`, treating argvalues as a list of tuples to unpack.\n\n#####
        Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
        Document safer alternatives and scope guidance for monkeypatching standard
        library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
        Document that `@pytest.hookimpl(specname=...)` only works for function names
        starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
        Document that doctests do not support parametrized fixtures, including parametrized
        autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
        Clarified how the `request` fixture provides indirect parametrization values
        via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
        Clarified in the documentation that hook implementations defined in `conftest.py`
        files are not available to other plugins during their `pytest_addoption()`
        execution, as conftest files are discovered and loaded after builtin and third-party
        plugins have been initialized. However, initial conftest files themselves
        can implement `pytest_addoption()` to add their own command-line options.\n-
        [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
        Clarified how subtest progress markers are shown in the documentation.\n-
        [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
        The `ini options ref` section of the API Reference now specified the type
        and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
        Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
        plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
        The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
        Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
        at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
        Pointing at a tag keeps the example in sync with the version users actually
        install, while remaining stable when the project's main branch moves on.\n\n#####
        Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
        Improved the recursion traceback test to exercise all requested traceback
        styles.\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
        (UTC)\n\n- Branch creation\n  - At any time (no schedule defined)\n- Automerge\n
        \ - At any time (no schedule defined)\n\n\U0001F6A6 **Automerge**: Disabled
        by config. Please merge this manually once you are satisfied.\n\n\u267B **Rebasing**:
        Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F515
        **Ignore**: Close this PR and you won't be reminded about this update again.\n\n---\n\n
        - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this
        box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
        View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-commons).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
      change_url: https://github.com/osism/ansible-collection-commons/pull/854
      child_jobs: []
      commit_id: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
      event_id: 322c8170-6778-11f1-9c30-4eb25741bad1
      executor:
        hostname: 521e9411259a
        inventory_file: /var/lib/zuul/builds/139e81f2aeb547108c8ffd7ab4711dad/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/139e81f2aeb547108c8ffd7ab4711dad/work/logs
        result_data_file: /var/lib/zuul/builds/139e81f2aeb547108c8ffd7ab4711dad/work/results.json
        src_root: /var/lib/zuul/builds/139e81f2aeb547108c8ffd7ab4711dad/work/src
        work_root: /var/lib/zuul/builds/139e81f2aeb547108c8ffd7ab4711dad/work
      include_vars: []
      items:
      - branch: main
        change: '854'
        change_message: "chore(deps): update dependency pytest to v9.1.0\n\nThis PR
          contains the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
          [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
          | `==9.0.3` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true)
          |\n\n---\n\n### Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
          [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
          pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
          changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/14533):
          When using `--doctest-modules`, autouse fixtures with `module`, `package`
          or `session` scope that are defined inline in Python test modules (not plugins
          or conftests) will now possibly execute twice.\n\n  If this is undesirable,
          move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
          explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
          pytest possibly collects Python modules twice, once as `pytest.Module` and
          once as a `DoctestModule` (depending on the configuration).\n  Due to improvements
          in pytest's fixture implementation, if e.g. the `DoctestModule` collects
          a fixture, it is now visible to it only, and not to the `Module`.\n  This
          means that both need to register the fixtures independently.\n\n##### Deprecations
          (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/10819):
          Added a deprecation warning for class-scoped fixtures defined as instance
          methods (without `@classmethod`). Such fixtures set attributes on a different
          instance than the test methods use, leading to unexpected behavior. Use
          `@classmethod` decorator instead -- by `yastcher`.\n\n  See `10819` and
          `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/12882):
          Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>`
          during teardown to request a fixture that was not already requested is now
          deprecated and will become an error in pytest 10.\n\n  See `dynamic-fixture-request-during-teardown`
          for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/13409):
          Using non-`~collections.abc.Collection` iterables (such as generators, iterators,
          or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize
          <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>`
          is now deprecated.\n\n  These iterables get exhausted after the first iteration,\n
          \ leading to tests getting unexpectedly skipped in cases such as running
          `pytest.main()` multiple times,\n  using class-level parametrize decorators,\n
          \ or collecting tests multiple times.\n\n  See `parametrize-iterators` for
          details and suggestions.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
          <pytest.Config.getini>` to access configuration values instead.\n\n  See
          `config-inicfg` for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture
          registration APIs is now deprecated. These are internal pytest APIs that
          are used by some plugins.\n\n  Use the `node` parameter instead for fixture
          scoping. This enables more robust node-based\n  matching instead of string
          prefix matching.\n  If you've used `nodeid=None`, pass `node=session` instead.\n\n
          \ This will be removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
          The method of configuring hooks using markers, deprecated since pytest 7.2,
          is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
          details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
          The `--pastebin` option is now deprecated.\n  The same functionality is
          now available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
          for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The private `FixtureDef.has_location` attribute is now deprecated and will
          be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for
          details.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
          \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
          New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
          Added `pytest.register_fixture()` to register fixtures using an imperative
          interface.\n\n  This is an advanced function intended for use by plugins.\n\n
          \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
          <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
          during the collection phase and registers them automatically.\n  For some
          plugin usecases the declarative interface can be cumbersome or unviable,
          in which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
          Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
          [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/14371):
          Added `--max-warnings` command-line option and `max_warnings` configuration
          option to fail the test run when the number of warnings exceeds a given
          threshold -- by `miketheman`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
          Added the `assertion_text_diff_style` configuration option, allowing\n  string
          equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
          instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/8395):
          Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons
          with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta`
          is required and relative tolerance is not supported for datetime comparisons
          -- by `hamza-mobeen`.\n\n##### Improvements in existing functionality\n\n-
          [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/11225):
          `pytest.warns` now shows \"Regex pattern did not match\" instead of \"DID
          NOT WARN\" when warnings were emitted but the `match` pattern did not match.\n\n-
          [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
          Improved output of `--fixtures-per-test` by excluding internal-implementation
          fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/13241):
          `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec`
          for the type hint to the (old and not recommended) callable overload, instead
          of `Any`. This allows type checkers to raise errors when passing incorrect
          function parameters.\n  `func` can now also be passed as a kwarg, which
          the type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
          Improved the readability of \"DID NOT RAISE\" error messages by using the
          exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
          [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
          Added test coverage for compiled regex patterns in `pytest.raises` match
          parameter.\n\n- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
          <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow
          using it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
          Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
          decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
          in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
          Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/14430):
          When using `--setup-show`, a space is now printed after the test name (and
          possibly used fixtures), to separate it from the test result.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/14441):
          Reduced the default number of `gc.collect()` passes in the `unraisableexception`
          plugin from 5 to 1 on CPython, where reference counting makes a single pass
          sufficient. PyPy retains 5 passes due to object resurrection via `__del__`.
          This can noticeably speed up test suites that trigger many pytester runs.\n\n-
          [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
          Improved assertion failure explanations for equality comparisons between
          mapping objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The order in which fixture definitions overriding each other are resolved
          is now determined first by their *visibility* in the collection tree rather
          than by the order in which they are registered.\n\n  A fixture defined for
          a more specific node (e.g. a module or an item) now always takes precedence
          over one with the same name defined for a more general node (e.g. the session),
          even when the more general one was registered later.\n  Fixtures with non-comparable
          visibility or the same visibility keep the existing behavior of \"last registered
          wins\".\n  This change is supposed to only affect plugins which register
          multiple fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
          Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          Improved argparse program name to show `pytest`, `python -m pytest`, or
          `pytest.main()` based on how pytest was invoked, making help and error messages
          clearer.\n\n- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
          Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
          `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
          this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
          pytest issues a helpful warning and continues collecting the module normally.\n\n#####
          Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
          Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
          meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
          [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
          Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
          [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
          Fixed function-scoped fixture values being kept alive after a test was interrupted
          by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be
          released more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
          Fixed `capteesys` producing doubled output when used with `--capture=no`
          (`-s`).\n\n- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
          Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
          the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
          Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
          being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
          Fixed autouse fixtures defined inside a `unittest.TestCase` class running
          even when the class is decorated with `unittest.skip` or `unittest.skipIf`
          -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
          `unittest.SkipTest` is no longer considered an interactive exception, i.e.
          `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
          Fixed subtests running with `pytest-xdist` when their contexts contain objects
          that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
          [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Fixed conftest.py fixture scoping when `testpaths` points outside of the
          `rootdir <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files
          would incorrectly leak to sibling directories\n  when using a relative `testpaths`
          like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
          <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
          [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
          Display dictionary differences in assertion failures using the original
          key insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
          fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
          methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
          An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
          from being torn down, causing additional errors in the following tests.\n\n-
          [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
          Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
          entry on the undo stack when the underlying `setattr()` call fails (e.g.
          on immutable targets), causing an `AttributeError` crash during teardown.\n\n-
          [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
          Fixed `-v` hint in `pytest.raises` match diff not working because assertion
          verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
          Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
          <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
          Fixed direct parametrization causing the static fixture closure (as reflected
          in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit
          fixtures that are requested transitively from overridden fixtures.\n\n-
          [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
          Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
          before pytest tears down the warning filters installed for the session.
          Previously the collection ran from a cleanup callback whose order relative
          to other plugins' cleanups was not guaranteed, so an active `error` filter
          could be removed before the exception surfaced and a late resource leak
          would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
          now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
          [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
          Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
          when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
          [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
          Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
          [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
          Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
          the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
          [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
          Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
          detection, causing the regex diff display to be shown in some instances
          when the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
          Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
          specified through `addopts` were silently ignored.\n\n  Note that when targeting
          pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
          `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
          Fixed `pytest.approx` not recognizing types with `__array_interface__` as
          numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
          Fixed a regression where `-k` and `-m` expressions containing both backslash
          characters in identifiers and string literal arguments would incorrectly
          raise a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
          Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
          plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
          [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
          Fixed `Code.getargs()` incorrectly including local variable names in the
          returned argument tuple for functions with `*args` and/or `**kwargs`. The
          method was using `co_flags` bitmask values (`4` and `8`) directly as counts
          instead of converting them to `1` via `bool()`, and was not accounting for
          `co_kwonlyargcount` when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
          Logging capture now works for non-propagating loggers.\n  Previously only
          logs which reached the root logger were captured.\n  This includes `caplog`
          and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
          Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
          now always matches the number of `<testcase>` elements in the file. In some
          cases (test passes but fails during teardown) the `tests` attribute would
          report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
          `pytest_fixture_post_finalizer` is no longer called extra times for the
          same fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
          Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
          single-element tuple values when using a string argnames with a trailing
          comma (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves
          like the tuple form `(\"arg\",)`, treating argvalues as a list of tuples
          to unpack.\n\n##### Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
          Document safer alternatives and scope guidance for monkeypatching standard
          library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
          Document that `@pytest.hookimpl(specname=...)` only works for function names
          starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
          Document that doctests do not support parametrized fixtures, including parametrized
          autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
          Clarified how the `request` fixture provides indirect parametrization values
          via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
          Clarified in the documentation that hook implementations defined in `conftest.py`
          files are not available to other plugins during their `pytest_addoption()`
          execution, as conftest files are discovered and loaded after builtin and
          third-party plugins have been initialized. However, initial conftest files
          themselves can implement `pytest_addoption()` to add their own command-line
          options.\n- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
          Clarified how subtest progress markers are shown in the documentation.\n-
          [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
          The `ini options ref` section of the API Reference now specified the type
          and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
          Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
          plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
          The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
          Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
          at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
          Pointing at a tag keeps the example in sync with the version users actually
          install, while remaining stable when the project's main branch moves on.\n\n#####
          Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
          Improved the recursion traceback test to exercise all requested traceback
          styles.\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
          (UTC)\n\n- Branch creation\n  - At any time (no schedule defined)\n- Automerge\n
          \ - At any time (no schedule defined)\n\n\U0001F6A6 **Automerge**: Disabled
          by config. Please merge this manually once you are satisfied.\n\n\u267B
          **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry
          checkbox.\n\n\U0001F515 **Ignore**: Close this PR and you won't be reminded
          about this update again.\n\n---\n\n - [ ] <!-- rebase-check -->If you want
          to rebase/retry this PR, check this box\n\n---\n\nThis PR was generated
          by [Mend Renovate](https://mend.io/renovate/). View the [repository job
          log](https://developer.mend.io/github/osism/ansible-collection-commons).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
        change_url: https://github.com/osism/ansible-collection-commons/pull/854
        commit_id: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
        patchset: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-commons
          name: osism/ansible-collection-commons
          short_name: ansible-collection-commons
          src_dir: src/github.com/osism/ansible-collection-commons
        topic: null
      job: python-black
      jobtags: []
      max_attempts: 3
      message: chore(deps): update dependency pytest to v9.1.0

This PR contains the following updates:

| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `==9.0.3` → `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/9.0.3/9.1.0?slim=true) |

---

### Release Notes

<details>
<summary>pytest-dev/pytest (pytest)</summary>

### [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)

[Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)

##### pytest 9.1.0 (2026-06-13)

##### Removals and backward incompatible breaking changes

- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/14533): When using `--doctest-modules`, autouse fixtures with `module`, `package` or `session` scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

  If this is undesirable, move the fixture definition to a `conftest.py` file if possible.

  Technical explanation for those interested:
  When using <span class="title-ref">--doctest-modules</span>, pytest possibly collects Python modules twice, once as `pytest.Module` and once as a `DoctestModule` (depending on the configuration).
  Due to improvements in pytest's fixture implementation, if e.g. the `DoctestModule` collects a fixture, it is now visible to it only, and not to the `Module`.
  This means that both need to register the fixtures independently.

##### Deprecations (removal in next major release)

- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/10819): Added a deprecation warning for class-scoped fixtures defined as instance methods (without `@classmethod`). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use `@classmethod` decorator instead -- by `yastcher`.

  See `10819` and `14011`.

- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/12882): Calling `request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>` during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

  See `dynamic-fixture-request-during-teardown` for details.

- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/13409): Using non-`~collections.abc.Collection` iterables (such as generators, iterators, or custom iterable objects) for the `argvalues` parameter in `@pytest.mark.parametrize <pytest.mark.parametrize ref>` and `metafunc.parametrize <pytest.Metafunc.parametrize>` is now deprecated.

  These iterables get exhausted after the first iteration,
  leading to tests getting unexpectedly skipped in cases such as running `pytest.main()` multiple times,
  using class-level parametrize decorators,
  or collecting tests multiple times.

  See `parametrize-iterators` for details and suggestions.

- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946): The private `config.inicfg` attribute is now deprecated.
  Use `config.getini() <pytest.Config.getini>` to access configuration values instead.

  See `config-inicfg` for more details.

- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004): Passing `baseid` to `~pytest.FixtureDef` or `nodeid` strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

  Use the `node` parameter instead for fixture scoping. This enables more robust node-based
  matching instead of string prefix matching.
  If you've used `nodeid=None`, pass `node=session` instead.

  This will be removed in pytest 10.

- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335): The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10.
  See `hook-markers` for more details.

- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434): The `--pastebin` option is now deprecated.
  The same functionality is now available in an external plugin, `pytest-pastebin`.
  See `pastebin-deprecated` for more details.

- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10.
  See `fixturedef-has-location-deprecated` for details.

- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764): `pytest.console_main` is now deprecated and will be removed in pytest 10.
  It was never intended for programmatic use; use `pytest.main` instead.

##### New features

- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376): Added `pytest.register_fixture()` to register fixtures using an imperative interface.

  This is an advanced function intended for use by plugins.

  Normally, fixtures should be registered declaratively using the `@pytest.fixture <pytest.fixture>` decorator.
  Pytest looks for these fixture definitions during the collection phase and registers them automatically.
  For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used.

- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023): Added <span class="title-ref">--report-chars</span> long CLI option.

- [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/14371): Added `--max-warnings` command-line option and `max_warnings` configuration option to fail the test run when the number of warnings exceeds a given threshold -- by `miketheman`.

- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757): Added the `assertion_text_diff_style` configuration option, allowing
  string equality failures to be rendered as separate `Left:` and `Right:`
  blocks instead of `ndiff` output.

- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/8395): Added support for `~datetime.datetime` and `~datetime.timedelta` comparisons with `pytest.approx`. An explicit `abs` or `rel` tolerance as a `~datetime.timedelta` is required and relative tolerance is not supported for datetime comparisons -- by `hamza-mobeen`.

##### Improvements in existing functionality

- [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/11225): `pytest.warns` now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the `match` pattern did not match.

- [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar.

- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/13241): `pytest.raises`, `pytest.warns` and `pytest.deprecated_call` now uses `ParamSpec` for the type hint to the (old and not recommended) callable overload, instead of `Any`. This allows type checkers to raise errors when passing incorrect function parameters.
  `func` can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept.

- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its <span class="title-ref">repr</span>.

- [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter.

- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137): <span class="title-ref">pytest.ScopeName</span> is now public to allow using it in function signatures.

- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342): Marked `yield_fixture` as deprecated to type checkers using the `deprecated` decorator. Note it
  `has originally been deprecated <yield-fixture-deprecated>` in pytest 6.2 already.

- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373): Added type annotations for `pytest.approx`.

- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/14430): When using `--setup-show`, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result.

- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/14441): Reduced the default number of `gc.collect()` passes in the `unraisableexception` plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via `__del__`. This can noticeably speed up test suites that trigger many pytester runs.

- [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances.

- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered.

  A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later.
  Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins".
  This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name.

- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524): Add official Python 3.15 support.

- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer.

- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`.

  Previously this caused a cryptic `TypeError: got None instead of Mark` error.
  Now pytest issues a helpful warning and continues collecting the module normally.

##### Bug fixes

- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192): Fixed <span class="title-ref">|</span> (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.

- [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`.

- [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit,
  allowing them to potentially be released more promptly.

- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`).

- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817): Fixed a secondary <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize.

- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> being overridden in client code.

- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0.

- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it.

- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable.

  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).

- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`.

  Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
  when using a relative `testpaths` like `../tests/sdk`.

  Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping.

- [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order.

- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods.

- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests.

- [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown.

- [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated.

- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing.

- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures.

- [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order.

- [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377): Fixed crash in <span class="title-ref">Config.get\_terminal\_writer</span> when an assertion fails with the `terminalreporter` plugin disabled.

- [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381): Fixed `-V` (short form of `--version`) to properly display the current version.

- [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`.

- [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead.

- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored.

  Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`.

- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays.

- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping.

- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights`

- [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`.

- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697): Logging capture now works for non-propagating loggers.
  Previously only logs which reached the root logger were captured.
  This includes `caplog` and the "Captured log calls" test reporting.

- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file.

- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases.

- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`).

  The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack.

##### Improved documentation

- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022): Document safer alternatives and scope guidance for monkeypatching standard library functions.
- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`.
- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures.
- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`.
- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options.
- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902): Clarified how subtest progress markers are shown in the documentation.
- [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option.
- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148): Documented a safe `pytestconfig.cache` access pattern when the
  `cacheprovider` plugin is disabled.
- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303): The documentation is now built with Sphinx >= 9.
- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on.

##### Miscellaneous internal changes

- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582): Improved the recursion traceback test to exercise all requested traceback styles.

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-commons).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->

      patchset: 15a46c344fa31d047f1ddd282fea39c55bd97bdb
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 688445d15ac2c497396b682f69c57ccd484f5f25
          trusted/project_1/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 038dd8b856c62af4433c8477c5cb3d0480847059
          trusted/project_2/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: 0c74c57cedff2b36bb37ca68a5338d1c49991496
          untrusted/project_0/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: 0c74c57cedff2b36bb37ca68a5338d1c49991496
          untrusted/project_1/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 688445d15ac2c497396b682f69c57ccd484f5f25
          untrusted/project_2/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 038dd8b856c62af4433c8477c5cb3d0480847059
        playbooks:
        - path: untrusted/project_0/github.com/osism/zuul-jobs/playbooks/python-black/run.yml
          roles:
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/playbook_0/role_0/zuul-config
            link_target: untrusted/project_1/github.com/osism/zuul-config
            role_path: ansible/playbook_0/role_0/zuul-config/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/openinfra-zuul-jobs
            link_target: untrusted/project_2/github.com/osism/openinfra-zuul-jobs
            role_path: ansible/playbook_0/role_1/openinfra-zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/osism/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
      post_review: false
      post_timeout: null
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/osism/ansible-collection-commons
        name: osism/ansible-collection-commons
        short_name: ansible-collection-commons
        src_dir: src/github.com/osism/ansible-collection-commons
      projects:
        github.com/osism/ansible-collection-commons:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-commons
          checkout: main
          checkout_description: zuul branch
          commit: b2e8cf5ac1a96b9fd76dead5b682ec2a2f8526fb
          name: osism/ansible-collection-commons
          required: false
          short_name: ansible-collection-commons
          src_dir: src/github.com/osism/ansible-collection-commons
      ref: refs/pull/854/head
      resources: {}
      tenant: osism
      timeout: 1800
      topic: null
      voting: true
