Merge pull request #78037 from ankur0904:fix-documentation

PiperOrigin-RevId: 688830164
This commit is contained in:
TensorFlower Gardener 2024-10-22 23:20:12 -07:00
commit e859e7c8da
2 changed files with 7 additions and 6 deletions

View File

@ -234,7 +234,7 @@ There are two ways to run TensorFlow unit tests.
for the required packages. Alternatively, use the said
[tensorflow/build Docker images](https://hub.docker.com/r/tensorflow/build)
(`tensorflow/tensorflow:devel` and `tensorflow/tensorflow:devel-gpu` are no
longer supported for) development. Use TF SIG Build Dockerfiles in
longer supported for development). Use TF SIG Build Dockerfiles in
development to avoid installing the packages directly on your system (in
which case remember to change the directory from `/root` to `/tensorflow`
once you get into the running container so `bazel` can find the `tensorflow`
@ -254,15 +254,16 @@ There are two ways to run TensorFlow unit tests.
```
If the tests are to be run on the GPU:
* For TensorFlow versions starting from v.2.18.0:
Add the `cuda` option flag.
* For TensorFlow versions starting from v.2.18.0: Add the `cuda` option
flag.
```bash
export flags="--config=opt --config=cuda -k"
```
* For TensorFlow versions prior v.2.18.0:
Add CUDA paths to LD_LIBRARY_PATH and add the `cuda` option flag.
* For TensorFlow versions prior v.2.18.0: Add CUDA paths to
LD_LIBRARY_PATH and add the `cuda` option flag.
```bash
export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:$LD_LIBRARY_PATH"

View File

@ -166,7 +166,7 @@ vulnerabilities.
We recognize issues as vulnerabilities only when they occur in scenarios that we
outline as safe; issues that have a security impact only when TensorFlow is used
in a discouraged way (e.g. running untrusted models or checkpoints, data parsing
outside of the safe formats, etc.) are not treated as vulnerabilities..
outside of the safe formats, etc.) are not treated as vulnerabilities.
### Reporting process