[CI]: Validate the built testing-library wheel in OTel compatibility lanes

Offen
  • Stimmt etwas nicht?
#863 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
77/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, python
Bereich
ci-cd, testing

Rechercherichtung

Read .github/scripts/install_otel_test_wheels.py and the wheel lane configuration in pyproject.toml; then trace how the existing built_wheel and verify helpers select and validate artifacts. Update both lanes to install and verify the required local testing wheel while preserving released OTel 1.0.0 in the legacy lane. Done means both installed-wheel commands pass with artifact checks, focused installer coverage, and CONTRIBUTING.md naming all three distributions.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Split from PR #795 — match replay state to the service, reference commit f8ac9b4; baseline main is d7ae95571c44b18c2a2efdef9a308b1c916c5049. This issue owns one independently implementable slice of that PR. Start a focused branch from current main and port only this slice, rather than stacking on the full PR.

Problem and reproduction

The installed-wheel lanes build/test local core and OTel artifacts while the testing library can remain the published dependency. A PR changing runner behavior can therefore pass installed-package validation without exercising the testing implementation that will ship. This is a validation gap, separate from the five runtime behavior fixes in this split.

Build core, OTel, and testing wheels from the checkout, run the wheel lane, and inspect installed distributions and module paths. The testing distribution must be the built local wheel rather than an editable checkout or unrelated published version.

Scope and implementation
  • Extend the existing installer package list to include the testing wheel in both lanes.
  • Normal lane: install built core, OTel, and testing wheels. Legacy lane: install built core/testing while retaining the actual released OTel 1.0.0 distribution used by the rejection tests.
  • Reuse built_wheel and verify: assert a single matching wheel, noneditable installation, archive SHA-256, and installed source bytes under site-packages; keep pip check.
  • Update CONTRIBUTING.md to require building all three distributions. Do not add a separate environment or duplicate artifact-verification framework.

Primary code: install_otel_test_wheels.py; supporting references: pyproject.toml, CONTRIBUTING.md, otel_lifecycle_compatibility_test.py, and otel_legacy_registration_rejection_test.py.

Acceptance criteria
  • Both lanes install and verify the built testing-library wheel before executing their tests.
  • The normal lane uses built core/OTel/testing; the legacy lane still imports released OTel 1.0.0 and verifies its rejection by current core.
  • Missing/ambiguous wheels or mismatched installed hashes/source bytes fail validation instead of silently falling back to a published/editable package.
  • Add focused installer selection/verification coverage and exercise both real installed-wheel lanes.
  • Build instructions accurately name all required distributions.
Validation

From each core, OTel, and testing package directory, run hatch build. From the repository root, run:

hatch run test-wheel-otel:test
hatch run test-wheel-otel-legacy:test

Use CI-pinned Hatch 1.16.5 at the reference. Run focused installer tests and relevant lint checks. The full #795 wheel validation passed on Python 3.13.17 with 805 OTel tests, 12 lifecycle cases, and four legacy rejection cases; verify the smaller infrastructure-only PR on its own artifacts rather than reusing that claim.

Independence

This change can land on main before any behavior fix: it validates whatever testing implementation the checkout builds. No new OTel callback scenarios, runtime changes, feature-branch filters, or release-version changes are needed. The temporary #795/#796 workflow target filters are stack housekeeping, not a seventh issue, and should not be copied into this independent PR. The existing test_subject_uppercase linter-unit failure noted in #795 is unrelated and is not part of this issue.

Related issues in this split
Vorherrschende Sprache
Python
Sterne
58
Forks
32
Ø Merge
1 T. 6 Std.
Gemergte PRs (30 T.)
80

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus aws/aws-durable-execution-sdk-python

Alle Issues in aws/aws-durable-execution-sdk-python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.