SUMIN/HuggingFace_transformer
1
0
Fork 0
Code Issues Pull Requests Actions 7 Packages Projects Releases Wiki Activity

fix wrong path in some doc (#25658)

Browse Source 
* update

* check

---------

Co-authored-by: ydshieh <ydshieh@users.noreply.github.com>
This commit is contained in:
Yih-Dar
2023-08-23 08:34:30 +02:00
committed by GitHub
parent db58722084
commit 3d1edb6c5d
3 changed files with 18 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/source/en/testing.md
View File

@@ -112,7 +112,7 @@ pytest tests/test_optimization.py --collect-only -q
To run an individual test module:
```bash
pytest tests/test_logging.py
pytest tests/utils/test_logging.py
```
### Run specific tests
@@ -432,14 +432,14 @@ pytest --instafail
On a GPU-enabled setup, to test in CPU-only mode add `CUDA_VISIBLE_DEVICES=""`:
```bash
CUDA_VISIBLE_DEVICES="" pytest tests/test_logging.py
CUDA_VISIBLE_DEVICES="" pytest tests/utils/test_logging.py
```
or if you have multiple gpus, you can specify which one is to be used by `pytest`. For example, to use only the
second gpu if you have gpus `0` and `1`, you can run:
```bash
CUDA_VISIBLE_DEVICES="1" pytest tests/test_logging.py
CUDA_VISIBLE_DEVICES="1" pytest tests/utils/test_logging.py
```
This is handy when you want to run different tasks on different GPUs.
@@ -515,14 +515,14 @@ n_gpu = get_gpu_count() # works with torch and tf
To run the test suite on a specific torch device add `TRANSFORMERS_TEST_DEVICE="$device"` where `$device` is the target backend. For example, to test on CPU only:
```bash
TRANSFORMERS_TEST_DEVICE="cpu" pytest tests/test_logging.py
TRANSFORMERS_TEST_DEVICE="cpu" pytest tests/utils/test_logging.py
```
This variable is useful for testing custom or less common PyTorch backends such as `mps`. It can also be used to achieve the same effect as `CUDA_VISIBLE_DEVICES` by targeting specific GPUs or testing in CPU-only mode.
Certain devices will require an additional import after importing `torch` for the first time. This can be specified using the environment variable `TRANSFORMERS_TEST_BACKEND`:
```bash
TRANSFORMERS_TEST_BACKEND="torch_npu" pytest tests/test_logging.py
TRANSFORMERS_TEST_BACKEND="torch_npu" pytest tests/utils/test_logging.py
```
@@ -553,7 +553,7 @@ according captured output will usually be shown along with the failure traceback
To disable output capturing and to get the `stdout` and `stderr` normally, use `-s` or `--capture=no`:
```bash
pytest -s tests/test_logging.py
pytest -s tests/utils/test_logging.py
```
To send test results to JUnit format output:
@@ -567,7 +567,7 @@ py.test tests --junitxml=result.xml
To have no color (e.g., yellow on white background is not readable):
```bash
pytest --color=no tests/test_logging.py
pytest --color=no tests/utils/test_logging.py
```
### Sending test report to online pastebin service
@@ -575,7 +575,7 @@ pytest --color=no tests/test_logging.py
Creating a URL for each test failure:
```bash
pytest --pastebin=failed tests/test_logging.py
pytest --pastebin=failed tests/utils/test_logging.py
```
This will submit test run information to a remote Paste service and provide a URL for each failure. You may select
@@ -584,7 +584,7 @@ tests as usual or add for example -x if you only want to send one particular fai
Creating a URL for a whole test session log:
```bash
pytest --pastebin=all tests/test_logging.py
pytest --pastebin=all tests/utils/test_logging.py
```
## Writing tests
@@ -1214,7 +1214,7 @@ tf.random.set_seed(seed)
To start a debugger at the point of the warning, do this:
```bash
pytest tests/test_logging.py -W error::UserWarning --pdb
pytest tests/utils/test_logging.py -W error::UserWarning --pdb
```
## Working with github actions workflows