You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For all PRs that are created in vllm-gaudi repository all checks in CI are required:
6
+
- pre-commit & DCO
7
+
- HPU tests
8
+
- HPU Gaudi tests
9
+
10
+
### Pre-commit & DCO
11
+
To install run:
12
+
13
+
```pre-commit install```
14
+
15
+
This way all of your commits should be correctly formated and signed-off. If you need to manually sign off your commits, remember to use ```git commit -s``` to pass DCO.
16
+
17
+
### HPU tests
18
+
HPU tests consist of several unit tests:
19
+
- pre merge tests
20
+
- unit tests
21
+
- perf test
22
+
- feature tests
23
+
- e2e tests
24
+
25
+
All of the above tests are mandatory. Those tests operate in fast fail mode, meaning if one test fails, all of the others won't be triggered.
26
+
27
+
### HPU Gaudi tests
28
+
Additional Gaudi tests are expectd to pass, but aren't mandatory. Those tests are being run on internal Jenkins system, so results are internal only. Those tests can be run by CODEOWNERs and TESTOWNERs only.
29
+
30
+
## Docs Pull Requests
31
+
All PRs that do not interfere in code, like docstring changes or README updates can be merged without HPU tests and Gaudi tests. It is still required to pass pre-commit check.
32
+
33
+
## Hourly Checks and Tests
34
+
On vllm-gaudi repository hourly tests can be found in ```Hourly Commit Check and Tests``` under ```Actions``` tab. This tab also allows developers to manually trigger hourly tests on selected branch.
35
+
36
+
If the last hourly test is failing it means that vllm-gaudi main branch doesn't work with upstream newest main commit. To find last good commit check [last good commit](https://github.com/vllm-project/vllm-gaudi/blob/vllm/last-good-commit-for-vllm-gaudi/VLLM_STABLE_COMMIT).
37
+
38
+
Failing hourly checks will be fixed by developers as soon as possible.
39
+
40
+
## Troubleshooting
41
+
### Unreleated failures
42
+
Sometimes there may be some issues that are unreleated to your specific changes in code. Often causeb by connection problems. In this case failed checks should be reruned. Those errors are:
43
+
-```Error response from daemon: No such container```
44
+
-```ValueError: Unsupported device: the device type is 7.```
45
+
-```[Device not found] Device acquire failed.```
46
+
47
+
### Accuracy and functionality issues
48
+
Accuracy issues can be tracked in HPU Gaudi tests with gsm8k runs. If any check fails with accuracy - too low accuracy compare to the one measured, or functionality issues, the **PR can't be merged** until solved.
49
+
50
+
### Pre-commit failures
51
+
To run pre-commit test manually run:
52
+
53
+
```pre-commit run --show-diff-on-failure --color=always --all-files --hook-stage manual```
0 commit comments