chore(deps): update pytest requirement from <10.0,>=9.0.3 to >=9.1.0,<10.0 in /vhdbuilder/packer/test/pam

[dependabot]

Updates the requirements on pytest to permit the latest version.

Release notes

Sourced from pytest's releases.

9.1.0

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

• #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 --doctest-modules, 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)

• #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.

• #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.

• #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.

• #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.

• #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.

• #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.

• #14434: The --pastebin option is now deprecated.

... (truncated)

Commits

• b2522cf Prepare release version 9.1.0
• 368d2fc [refactor] Tighten SetComparisonFunction to Iterator[str] (#14587)
• ff77cd8 [refactor] Make base assertion comparisons return an iterator instead of a li...
• 0d8491a build(deps): Bump actions/stale from 10.2.0 to 10.3.0
• 4a809d9 Merge pull request #14568 from pytest-dev/register-fixture
• 5dfa385 Fix recursion traceback test to cover all styles (#14582)
• f52ff0c Add pytest.register_fixture
• a8ac094 Merge pull request #14567 from pytest-dev/more-visibility-deprecate
• e5620cd [pre-commit.ci] pre-commit autoupdate (#14577)
• 2ce9c6d Merge pull request #14540 from minbang930/fix-14533-doctest-module-fixtures
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

🕵️ AgentBaker Linux Gate Detective — Build 168010367 (Run AgentBaker E2E) FAILED — known shared-cluster infra outage, not caused by this PR.

TL;DR

Matches wiki signature shared-cluster-fleet-outage — broad cross-cluster kube.go:195 600-1500s pre-kubelet-registration timeouts, this time on abe2e-azure-overlay-network-v4-b4fc3 (westus3). Repair item #38373323 is already tracking. This PR (a pytest requirement bump in /vhdbuilder/packer/test/pam) only affects Packer-time test deps, has no path to kubelet/CSE/apiserver — diff cannot cause E2E node-registration timeouts.

3-level RCA

1. Surface symptom — 236 failures in Run AgentBaker E2E (414 tests, 97 skipped); failed scenarios uniformly terminate at kube.go:195 🔴 FAIL: "<vmss>" haven't appeared in k8s API server: context deadline exceeded after ~740s. Failures span shared cluster abe2e-azure-overlay-network-v4-b4fc3 (rg abe2e-westus3).

2. Corroboration — kubenet-v5-node-not-ready-scriptless (repair item #38403603) hit the same pre-kubelet-registration symptom across 18+ unrelated builds on adjacent shared clusters over the last 48h. The broader shared-cluster-fleet-outage (#38373323) has 16 prior builds spanning 12+ shared cluster families including azure-network-v4, overlay-network-v4, networkisolated-v3, kubenet-v5. Identical fingerprint here.

3. Root-cause challenge — Strongest alternative: PR-caused regression via the pytest bump (<10.0,>=9.0.3 → >=9.1.0,<10.0). Why less likely: the bump is scoped to vhdbuilder/packer/test/pam (PAM-related Packer-time Python tests) — runs inside the Packer VHD-build phase, not the post-build Go-based AgentBaker E2E job. E2E run uses pre-built VHDs and Go tests; pytest doesn't enter that codepath. Failure point is pre-kubelet-registration on shared cluster apiservers — no plausible mechanism from a Python test dep bump.

Classification

• Test infrastructure / shared-cluster fleet stress (not PR-caused)
• Wiki signature: shared-cluster-fleet-outage (Count → 17 distinct builds incl. this one)
• Confidence: High.

Recommended next action

• For this PR: safe to rerun the gate once shared clusters recover; no code change required.
• Owner of the underlying issue: AgentBaker E2E test-infra (repair item #38373323).

Evidence

• Failed run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=168010367
• Failed job: Run AgentBaker E2E (e2e stage)
• Test summary: 414 tests, 97 skipped, 236 failures in 2202.5s
• Teams escalation thread (related kubenet-v5 sub-signature): WS - CI - CD - E2E - CVE

Posted by Clawpilot AgentBaker Linux Gate Detective Watcher.