Skip to content

[v636] Backport fixes #19158

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

Merged
merged 3 commits into from
Jun 24, 2025
Merged

Conversation

guitargeek
Copy link
Contributor

Backport fixes to the current release branch.

guitargeek and others added 3 commits June 25, 2025 00:24
Right now we don't support the newest TensorFlow releases after the 2.15
series, initially released in November 2023 [1].

Support for TensorFlow>=2.16 is worked on [2], but it's difficult to
make progress if we don't have TensorFlow>=2.16 in our CI images.
And we veto it from our CI image via the `requirements.txt` mechanism.

To continue, we need to temporarily disable PyMVA in the CI, such that
we can include the newest TensorFlow version in our images, and then
re-enable it in the PR that fixes support for the newest TensorFlow.
This is what is done in this commit.

Supporting the newest TensorFlow became a bit more important now that we
also have another feature besides PyMVA that uses TensorFlow: the
RBatchGenerator. It would not good to hold off testing the
actively-developed RBatchGenerator on newer TensorFlow versions, just
because PyMVA prevents us from installing these on our CI.

[1] https://github.com/tensorflow/tensorflow/releases
[2] root-project#15790
Correctly append the additional RPATHs set by the ROOT build system to
the `CMAKE_INSTALL_RPATH` variable set by the user, which is cached in
`CMAKE_INSTALL_RPATH-CACHED` by the ROOT build system.

Follows up on c77bd87.

Closes root-project#19134.

Needs a backport to 6.36.
@guitargeek guitargeek self-assigned this Jun 24, 2025
@guitargeek guitargeek merged commit 95ab3c5 into root-project:v6-36-00-patches Jun 24, 2025
19 of 22 checks passed
@guitargeek guitargeek deleted the bp_1 branch June 24, 2025 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants