forked from tensorflow/tensorflow
-
Notifications
You must be signed in to change notification settings - Fork 95
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
find rocm components individually #2566
Closed
afzpatel
wants to merge
200
commits into
ROCm:develop-upstream
from
afzpatel:find-rocm-components-individually
Closed
find rocm components individually #2566
afzpatel
wants to merge
200
commits into
ROCm:develop-upstream
from
afzpatel:find-rocm-components-individually
Conversation
This file contains 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
* Insert release notes place-fill * Update RELEASE.md --------- Co-authored-by: Raviteja Gorijala <36429068+rtg0795@users.noreply.github.com>
…umbers-2.14.0rc0-12810 Update version numbers for TensorFlow 2.14.0-rc0
r2.14 cherry-pick: 63d1596 "version bump and formatting"
Update setup.py on TF release branch with released version
XLA unit tests were unable to link due to undefined reference to stream_executor::Stream::BlockHostUntilDone()
r2.14 cherry-pick: de4a9a8 "Fix link failure in XLA unit tests"
Update requirements.in to bump keras-nightly and tf-estimator-nightly
Run requirements updater to bump keras, tb and estimator
PiperOrigin-RevId: 554977992 Co-authored-by: Adrian Revuelta <adrianrc@google.com>
Update Windows Release Build File
This reverts commit 93f0215.
Revert "Update Windows Release Build File"
…umbers-2.14.0rc1-30454 Update version numbers for TensorFlow 2.14.0-rc1
Update requirements_lock.txt files
…corrupted PT_NOTE program headers. It seems that using Patchelf <0.12 during the [wheel building process](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/pip_package/build_pip_package.sh#L255-L262) corrupts the PT_NOTE program headers of certain shared libraries. Upgrading the patchelf version seems to fix this. We need to download the latest version from GitHub because the default Ubuntu Focal packages only provide the "0.10-2build1" version. PiperOrigin-RevId: 560754278
It has been deprecated since 2019, and is now triggering warnings on TensorFlow startup. It does, however, still need to be included in `python/__init__.py` so that it can be found by `tf.compat.v1.distributions`, which several projects depend on. We will remove the entire package from TensorFlow as a follow-up. But at the moment, doing so would break too many other projects. PiperOrigin-RevId: 558816905
fixed navi bugs
Merge pull request ROCm#2450 from ROCm/navi_bug r2.14
[r2.14-rocm-enhanced][ROCm] Allow XLA LLVM to read rocm 6.2 'libdevice' bitcode files
…wd (ROCm#2474) This change is helping to permanently get rid of below issue. 02:56:54 Step 29/38 : RUN echo 'ALL ALL=NOPASSWD:ALL' | tee /etc/sudoers.d/sudo-nopasswd 02:56:54 ---> Running in f871d0cf3b96 02:56:54 �[91mtee: /etc/sudoers.d/sudo-nopasswd: No such file or directory 02:56:54 �[0mALL ALL=NOPASSWD:ALL 02:56:54 The command '/bin/sh -c echo 'ALL ALL=NOPASSWD:ALL' | tee /etc/sudoers.d/sudo-nopasswd' returned a non-zero code: 1
…_fix [r2.14-rocm-enhanced][ROCM] adding env variable to control rocm_dnn workspace limit
[r2.14-rocm-enhanced] Include numpy WAR in run_cpu.sh script
[ROCM][R2.14-rocm-enhanced] Workaround for TF issue 62466
…t-build no hipblas-lt build protection
[r2.14-rocm-enhanced] Adjust rocm-smi check for test scripts
r2.14-rocm-enhanced - skipping mgpu test in sgpu script
[r2.14-rocm-enhanced] Update 2.14 branch to 2.14.1
[r2.14-rocm-enhanced] Fix a typo in setup.rocm.cs7.sh
@afzpatel Can you please add this to develop-upstream and trigger CI. Once CI passes we can backport that change to all the other required branches. |
afzpatel
changed the base branch from
r2.14-rocm-enhanced-spack
to
develop-upstream
June 10, 2024 18:33
woops changing the base got the pr really messy, gonna close this and open a new one |
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.
Required for spack since all the rocm components are located in different paths