Currently, `no_oss` is used to exclude a test from running in the official TF OSS test infrastructure. However, it is difficult to distinguish between temporary and permanent exclusions. For example, a test may be disabled temporarily if it is broken, or it may be designed to not run on OSS permanently. To address this issue, we introduce a new tag `oss_excluded` for platform exclusion design. `no_oss` will now be considered to disable broken tests, while `oss_excluded` will be used to permanently exclude a test from running on OSS.
PiperOrigin-RevId: 516372702
Currently, `no_windows` is used to exclude a test from running in the windows environment. However, it is difficult to distinguish between temporary and permanent exclusions. For example, a test may be disabled temporarily if it is broken, or it may be designed to not run on windows environment permanently. To address this issue, we introduce a new tag `windows_excluded` for platform exclusion design. `no_windows` will now be considered to disable broken tests, while `windows_excluded` will be used to permanently exclude a test from running on windows environment.
PiperOrigin-RevId: 515716934
Currently, `no_mac` or `nomac` is used to exclude a test from running in the mac environment. However, it is difficult to distinguish between temporary and permanent exclusions. For example, a test may be disabled temporarily if it is broken, or it may be designed to not run on mac environment permanently. To address this issue, we introduce a new tag `mac_excluded` for platform exclusion design. `no_mac` or `nomac` will now be considered to disable broken tests, while `mac_excluded` will be used to permanently exclude a test from running on mac environment.
PiperOrigin-RevId: 515676485
-Switch ROCm builds to use ROCm5.2
-Fix Tensorflow build failure with ROCm 5.2, due to new templates in rocmprim header
-Changes related to hipsparse build failure fix.
-Changes related to hipsolver/rocsolver build failure fix.
-Removing the setting of ROCBLAS_TENSILE_LIBPATH in configure.py
-Update install_bazel script to match .bazelversion
The commit 3484416b49 removed the
'rules_cc_toolchains' call from the bazel configuration. After that,
the build process is calling 'lld' to link several binaries, causing
problems on ppc64le arch.
This patch set the 'gold' linker as default in the configure script.
Eigen removed the dynamic dispatch by default. Now, it's necessary to add
EIGEN_ALTIVEC_ENABLE_MMA_DYNAMIC_DISPATCH=1 to enable this feature if
the linker version is 2.35 or greater.
7b10795e39591906477b
These checks were useful when we used to set the bazel version in the CI scripts but now that we have `.bazelversion` synced in the repo any user using Bazelisk or a recent version of Bazel will automatically get the exact Bazel version that we are using. Hence, this step in `configure.py` is no longer needed.
Furthermore, we are working on completely removing the need to run `configure.py`, at least for the vast majority of users.
PiperOrigin-RevId: 448033791
Since TF is in the progress of migrating to `cc_shared_library`, we are stress testing Bazel and uncovering a large number of bugs. We are in the state where some TF builds are broken with cascading failures and there is a long wait until a new LTS Bazel release. So, we're switching to rolling releases in an attempt to fix the builds.
However, if this causes more failures than it resolves, we will need to return back to stable releases.
PiperOrigin-RevId: 445259819
This is not actually used but to prevent confusion let's bring it up to date
PiperOrigin-RevId: 427769347
Change-Id: I1ebc7797a337b98135ee038bb8c5840c8c7c7b3c
`.bazelversion` specifies the Bazel version that TensorFlow uses. This changelist updates the Bazel version from 4.2.2 to 5.0.0. It also updates the CI environment.
PiperOrigin-RevId: 424897733
Change-Id: Idd427ee8b1fdc8212211fb22c25989cb47350ab4
This PR is to address the TF build failure reported in JIRA ticket:
http://ontrack-internal.amd.com/browse/SWDEV-241967
The valid set of values for the env var HIP_PLATFORM is being updated, and as a consequence `hcc` will no longer a valid value (staring with ROCm 3.7).
For ROCm 3.7, we will need to change the configure.py script such that the env var HIP_PLATFORM=amd is explicitly when invoked with TF_NEED_ROCM=1.
In the meantime (i.e. until we switch to ROCm 3.7), we need to provide a way for passing HIP_PLATFORM to bazel (to help QA in testing ROCm 3.7). This change provides that way.
If the HIP_PLATFORM env var is set in the shell that invokes the "configure.py" script, it will pass it through to bazel.
These are a holdover from the transition from Python 2.* to Python 3.*.
PiperOrigin-RevId: 399530502
Change-Id: I1c8b893fd7f5eeb5eb51b2e2c38c3b73ec5b9903
