Repository: modelscope/evalscope
Issue: [BUG] Failed to parse usage from response: list index out of range. Response: []
Root cause: Validation Gap

## 自查清单

在提交 issue 之前，请确保您已完成以下步骤:
- [ ] 我已仔细阅读了[相关使用说明文档](https://evalscope.readthedocs.io/zh-cn/latest/get_started/parameters.html)
- [ ] 我已查看了[常见问题解答](https://evalscope.readthedocs.io/zh-cn/latest/get_started/faq.html)
- [ ] 我已搜索并查看了现有的 issues，确认这不是一个重复的问题

## 问题描述

Failed to parse usage from response: list index out of range. Response: []

## EvalScope 版本（必填）
1.3.0

## 使用的工具
- [ ] Native / 原生框架
- [ ] Opencompass backend
- [ ] VLMEvalKit backend
- [ ] RAGEval backend
- [x] Perf / 模型推理压测工具
- [ ] Arena / 竞技场模式

## 执行的代码或指令

```bash
evalscope perf   --parallel 20   --number 20   --model deepseek   --log-every-n-query 100   --url http://127.0.0.1:1025/v1/chat/completions   --api openai   --dataset random   --prefix-length 0   --tokenizer-path /workspace/cache/aiops-sh2/models/DeepSeek-V3.2-Exp-W8A8    --extra-args '{"ignore_eos": true}'   --min-prompt-length 7000   --max-prompt-length 7000   --max-tokens 2000   --min-tokens 2000
```

## 错误日志

```bash
Processing:   0%|                                                                                        | 0/20 [00:00<?, ?it/s]
2025-12-12 17:21:52 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:   5%|███▊                                                                         | 1/20 [05:43<1:48:47, 343.56s/it]
2025-12-12 17:22:04 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  10%|███████▉                                                                       | 2/20 [05:56<44:40, 148.91s/it]
2025-12-12 17:22:05 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  15%|████████████                                                                    | 3/20 [05:56<22:58, 81.10s/it]
2025-12-12 17:22:13 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  20%|████████████████                                                                | 4/20 [06:05<13:58, 52.42s/it]
2025-12-12 17:22:19 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  25%|████████████████████                                                            | 5/20 [06:11<08:57, 35.82s/it]
2025-12-12 17:22:23 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  30%|████████████████████████                                                        | 6/20 [06:15<05:49, 24.98s/it]
2025-12-12 17:22:26 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  35%|████████████████████████████                                                    | 7/20 [06:17<03:49, 17.63s/it]
2025-12-12 17:22:27 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  40%|████████████████████████████████                                                | 8/20 [06:18<02:27, 12.28s/it]
2025-12-12 17:22:28 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  45%|████████████████████████████████████                                            | 9/20 [06:19<01:35,  8.70s/it]
2025-12-12 17:22:29 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  50%|███████████████████████████████████████▌                                       | 10/20 [06:20<01:03,  6.39s/it]
2025-12-12 17:22:37 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  55%|███████████████████████████████████████████▍                                   | 11/20 [06:29<01:03,  7.04s/it]
2025-12-12 17:22:38 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  60%|███████████████████████████████████████████████▍                               | 12/20 [06:29<00:40,  5.04s/it]
2025-12-12 17:22:42 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  65%|███████████████████████████████████████████████████▎                           | 13/20 [06:33<00:32,  4.67s/it]
2025-12-12 17:22:44 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  70%|███████████████████████████████████████████████████████▎                       | 14/20 [06:36<00:24,  4.11s/it]
2025-12-12 17:22:47 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  75%|███████████████████████████████████████████████████████████▎                   | 15/20 [06:39<00:18,  3.68s/it]
2025-12-12 17:22:50 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  80%|███████████████████████████████████████████████████████████████▏               | 16/20 [06:42<00:14,  3.50s/it]
2025-12-12 17:25:11 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  85%|███████████████████████████████████████████████████████████████████▏           | 17/20 [09:02<02:14, 44.79s/it]
2025-12-12 17:25:18 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  90%|███████████████████████████████████████████████████████████████████████        | 18/20 [09:10<01:07, 33.52s/it]
2025-12-12 17:25:19 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing:  95%|███████████████████████████████████████████████████████████████████████████    | 19/20 [09:11<00:23, 23.72s/it]
2025-12-12 17:25:21 - evalscope - ERROR: Failed to parse usage from response: list index out of range. Response: []
Processing: 100%|███████████████████████████████████████████████████████████████████████████████| 20/20 [09:13<00:00, 27.67s/it]
2025-12-12 17:25:21 - evalscope - INFO: 
Benchmarking summary:
+-----------------------------------+----------+
| Key                               |    Value |
+===================================+==========+
| Time taken for tests (s)          | 553.265  |
+-----------------------------------+----------+
| Number of concurrency             |  20      |
+-----------------------------------+----------+
| Total requests                    |  20      |
+-----------------------------------+----------+
| Succeed requests                  |  20      |
+-----------------------------------+----------+
| Failed requests                   |   0      |
+-----------------------------------+----------+
| Output token throughput (tok/s)   |   0      |
+-----------------------------------+----------+
| Total token throughput (tok/s)    |   0      |
+-----------------------------------+----------+
| Request throughput (req/s)        |   0.0363 |
+-----------------------------------+----------+
| Average latency (s)               | 412.646  |
+-----------------------------------+----------+
| Average time to first token (s)   | 412.646  |
+-----------------------------------+----------+
| Average time per output token (s) |   0      |
+-----------------------------------+----------+
| Average inter-token latency (s)   |   0      |
+-----------------------------------+----------+
| Average input tokens per request  |   0      |
+-----------------------------------+----------+
| Average output tokens per request |   0      |
+-----------------------------------+----------+
2025-12-12 17:25:21 - evalscope - INFO: 
Percentile results:
+-------------+----------+---------+----------+-------------+--------------+---------------+----------------+---------------+
| Percentiles | TTFT (s) | ITL (s) | TPOT (s) | Latency (s) | Input tokens | Output tokens | Output (tok/s) | Total (tok/s) |
+-------------+----------+---------+----------+-------------+--------------+---------------+----------------+---------------+
|     10%     | 356.616  |   nan   |   0.0    |   356.616   |      0       |       0       |      0.0       |      0.0      |
|     25%     | 375.4048 |   nan   |   0.0    |  375.4048   |      0       |       0       |      0.0       |      0.0      |
|     50%     | 389.2774 |   nan   |   0.0    |  389.2774   |      0       |       0       |      0.0       |      0.0      |
|     66%     | 396.3652 |   nan   |   0.0    |  396.3652   |      0       |       0       |      0.0       |      0.0      |
|     75%     | 402.1504 |   nan   |   0.0    |  402.1504   |      0       |       0       |      0.0       |      0.0      |
|     80%     | 542.9655 |   nan   |   0.0    |  542.9655   |      0       |       0       |      0.0       |      0.0      |
|     90%     | 551.1144 |   nan   |   0.0    |  551.1144   |      0       |       0       |      0.0       |      0.0      |
|     95%     | 553.2551 |   nan   |   0.0    |  553.2551   |      0       |       0       |      0.0       |      0.0      |
|     98%     | 553.2551 |   nan   |   0.0    |  553.2551   |      0       |       0       |      0.0       |      0.0      |
|     99%     | 553.2551 |   nan   |   0.0    |  553.2551   |      0       |       0       |      0.0       |      0.0      |
+-------------+----------+---------+----------+-------------+--------------+---------------+----------------+---------------+
```

## 运行环境

- 操作系统：
- Python版本：

## 其他信息

如果有其他相关信息，请在此处提供。


你的模型接口是否能正常调用，一般不会返回空的列表

> 你的模型接口是否能正常调用，一般不会返回空的列表
我curl了，单个请求是可以的，不知道为啥会出现这种情况

贴一下返回的格式，是否是openai api格式