Use consistent abseil version in TensorFlow #8672
Closed
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.
The change to the abseil version in #8565 introduced an inconsistency in TensorFlow, leading to errors like this:
The problem as I understand it:
lts_20220623rather thanlts_20230125).bazel-absl.patchfile that updates the central Bazel info on this package.I patched all the places I could find where the Bazel version was hardcoded in the TensorFlow source (based on the upstream abseil version update in TensorFlow 2.13.0, one minor version after ours: tensorflow/tensorflow@ad938db) and was able to remove the
DeepMETProducerworkaround from cms-sw/cmssw#42228 (see cms-sw/cmssw#42682). I'm happy to reimplement the patches in whatever way is preferred (but it's going to be ugly no matter what).attn: @iarspider @yongbinfeng