-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix CL tests #7074
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
psamanoelton
wants to merge
2
commits into
tensorflow:master
Choose a base branch
from
psamanoelton:fix_cl
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+93
−62
Open
Fix CL tests #7074
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this error is basically making evident that the protos used are not compatible with the environment where they're used.
Changing the way this validation is done just works around the incompatibility that uses could otherwise encounter, although to be honest, I'm not sure how likely this is to be an issue.
I would prefer to try to make the assertProtoEquals work (I think this will result in the challenging dependency update that I encountered before).
If we can't get it to work, we can consider adding this workaround for now, but adding a short comment clarifying why the asserProtosEqual is not being used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion — I also tried to see if we could keep using
assertProtoEquals.The issue appears to come from the protobuf runtime installed in the current test environment. CI installs tf-nightly, which pulls in protobuf 7.x. In that version the FieldDescriptor.label attribute is no longer available:
Has FieldDescriptor.label: FalseHowever, TensorFlow’s
assertProtoEqualshelper still relies on that attribute internally, which causes it to fail before actually comparing the protos:AttributeError: 'google._upb._message.FieldDescriptor' object has no attribute 'label'Since tf-nightly requires a recent protobuf version, fixing this by pinning protobuf to an older version would likely require broader dependency or workflow changes.
I also added a short comment in the test explaining why assertProtoEquals is avoided here.
If you prefer, we could also explore restoring
assertProtoEqualsthrough a dependency adjustment or compatibility patch in a follow-up change.