Update TFX-bsl and TFMD version constraints in setup.py to its master and pinning Bazel version to 7.7.0#349
Merged
Merged
Conversation
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
This PR updates the
tfx-bslandtfmddependency references to point to the official repository'smasterbranch and introduces stability fixes to the GitHub Actions workflows to resolve Bazel and PIP build isolation conflicts.Key Changes
1. Dependency Cleanups (
setup.py)tfx-bslto Master: Reverted testing fork references and pointed thetfx-bslandtfmdgit references to the officialtensorflow/tfx-bsl@mastertensorflow/metadata@masterbranchs.2. CI Workflow Stability Fixes (
.github/workflows/)Bazel Version Pinning: Set
USE_BAZEL_VERSION: 7.7.0globally in both theci-test.ymlandwheels.ymlenvironments. This prevents the runner from downloading incompatible newer versions of Bazel (e.g.,9.x) that cause build errors (such asname 'sh_binary' is not defined) during dependency compilation.Bypass Build Isolation Conflicts:
setuptools,wheel,numpy, andpyarrow) in the runner environment.--no-build-isolation(e.g.,pip install --no-build-isolation .[test]).--no-isolation(e.g.,python -m build --no-isolation).Reasoning: This completely avoids PEP 517 isolated environment setups where pip-generated
sitecustomize.pyassertions (assert not path in sys.path) collide with environmentPYTHONPATHvariables forwarded by Bazel's sandboxed sub-shells.Verification & Status