test: e2e matrix entry for local.py config_dev branch#18
Merged
Conversation
be96234 to
1e10329
Compare
54a80a6 to
57b562e
Compare
Contributor
Author
|
hi @trisdoan
|
…or config Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add an explicit actions/cache step for /opt/hostedtoolcache/uv before
setup-uv in both test-native and test-oca jobs. setup-uv runs before
checkout so it can't resolve the version from pyproject.toml and falls
back to a GitHub Releases download every time. Caching the binary with
a static key (uv-binary-${{ runner.os }}-0.10.8) lets warm runs skip
the download entirely.
Also pin uv to 0.10.8 and add ignore-empty-workdir: true to suppress
the "could not find uv.toml/pyproject.toml" warnings.
51728b5 to
edf547c
Compare
mysql-python is a Python 2-only package that cannot be built on Python 3. Drop it from _NO_BUILD_ISOLATION_PACKAGES and the _NBI_BUILD_DEPS ConfigParser hack (ConfigParser on PyPI is Python 2-only and cannot be installed on Python 3.7+). Also correct the _MANIFEST_IMPORT_TO_PIP mapping for the `MySQLdb` import name: the Python 3-compatible package is `mysqlclient`, not `MySQL-python`. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
cf93527 to
3ae2195
Compare
…s legacy setuptools magento (v3.1) depends on suds-jurko, which fails to build with setuptools>=58 (use_2to3 removed). Since suds-jurko was only a transitive dep, the existing _NO_BUILD_ISOLATION_PACKAGES scan never detected it and it was built in isolation with modern setuptools during the batch install. Adding magento to _NO_BUILD_ISOLATION_PACKAGES (odoo_version <= 13.0) excludes it from the batch install and re-installs it with --no-build-isolation after setuptools<58 is in place, so uv uses the venv's build tools for all packages in that invocation (including suds-jurko). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
90204eb to
a0e1a66
Compare
pandas>=1.0 depends on python-dateutil>=2.7.3 and pytz>=2017.3, but Odoo<=13 pins python-dateutil==2.5.3 and pytz==2016.7. Without relaxing both, the resolver walks every pandas version down to 0.13.1 and fails on its invalid pytz>=2011k specifier. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
altair depends on pandas, which needs python-dateutil>=2.7.3 and pytz>=2017.3. Since pandas is only a transitive dep, altair needs its own _KNOWN_TRANSITIVE_CONFLICTS entry. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Every klaviyo-api version requires requests>=2.26.0, but Odoo<=13 pins requests==2.20.0. No compatible version exists without relaxing the pin. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
e0386ab to
03c0285
Compare
trisdoan
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
All previously stacked PRs have been merged into main. This PR now contains the remaining e2e infrastructure commits plus fixes for legacy Odoo dependency resolution issues discovered during testing.
E2E infrastructure
test-ocajob that tests with the full OCA contributor module set using the auto-generated per-version repo list fromtrobz/odoo-addons-repostest-nativeandtest-ocajobs to avoid GitHub Releases downloads on warm runs; also pins uv to 0.10.8 and addsignore-empty-workdir: trueDependency resolution fixes (Odoo ≤13 + OCA addons)
fix: handle magento as NBI package —
magentodepends onsuds-jurko, which needs--no-build-isolation+ legacysetuptools<58. Sincesuds-jurkois a transitive dep (not in direct requirements), PR feat: auto-handle packages requiring --no-build-isolation #44's scan never detected it. Addingmagentoto_NO_BUILD_ISOLATION_PACKAGESensures it and its transitive deps are built with the venv's legacy setuptools.fix: relax python-dateutil and pytz pins when pandas is required —
pandas>=1.0needspython-dateutil>=2.7.3andpytz>=2017.3, but Odoo ≤13 pins==2.5.3and==2016.7respectively. Without relaxing both, the resolver walks every pandas version down to 0.13.1 and fails on its invalidpytz>=2011kspecifier. Adds"pandas": ["python-dateutil", "pytz"]to_KNOWN_TRANSITIVE_CONFLICTS.fix: relax python-dateutil and pytz pins when altair is required —
altair→pandas→python-dateutil>=2.7.3+pytz>=2017.3. Sincepandasis only a transitive dep ofaltair, the user-source scan won't find it —altairneeds its own entry:"altair": ["python-dateutil", "pytz"].fix: relax requests pin when klaviyo-api is required — Every
klaviyo-apiversion requiresrequests>=2.26.0, but Odoo ≤13 pins==2.20.0. No compatible version exists without relaxing the pin. Adds"klaviyo-api": ["requests"].🤖 Generated with Claude Code