Repository: modelscope/evalscope
Issue: KeyError: 'metric_name' when evaluating against HLE
Root cause: Validation Gap

## 自查清单

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

## 问题描述

```
KeyError: 'metric_name' when evaluating against HLE 
```

## EvalScope 版本（必填）
v1.2.0

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

## 执行的代码或指令
```bash
evalscope eval \
  --eval-type openai_api \
  --eval-batch-size 16 \
  --datasets "${DATASETS[@]}" \
  --model "$MODEL" \
  --api-url "$API_URL"/v1 \
  --api-key "$API_KEY" \
  --work-dir "evalscope/${MODEL}" \
  --use-cache "evalscope/${MODEL}" \
  --seed 6611 \
  --timeout 30 \
  --stream \
  --generation-config max_tokens=2048,reasoning_effort=medium \
  --ignore-errors \
  --analysis-report
```

## 错误日志

```
2025-11-18 14:39:28 - evalscope - INFO: Aggregating scores for subset: Other
2025-11-18 14:39:28 - evalscope - INFO: Generating report...
Traceback (most recent call last):
  File "/opt/miniconda3/envs/llm/bin/evalscope", line 8, in <module>
    sys.exit(run_cmd())
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/cli/cli.py", line 27, in run_cmd
    cmd.execute()
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/cli/start_eval.py", line 32, in execute
    run_task(self.args)
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/run.py", line 28, in run_task
    return run_single_task(task_cfg, run_time)
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/run.py", line 42, in run_single_task
    result = evaluate_model(task_cfg, outputs)
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/run.py", line 148, in evaluate_model
    res_dict = evaluator.eval()
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/evaluator/evaluator.py", line 111, in eval
    report = self.get_report(agg_score_dict)
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/evaluator/evaluator.py", line 367, in get_report
    report = self.benchmark.generate_report(
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/api/benchmark/adapters/default_data_adapter.py", line 748, in generate_report
    report = self._on_generate_report(scores, model_name=model_name)
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/api/benchmark/adapters/default_data_adapter.py", line 728, in _on_generate_report
    return ReportGenerator.generate_report(
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/evalscope/report/generator.py", line 101, in generate_report
    for metric_name, group_metric in df.groupby('metric_name', sort=False):
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/pandas/core/frame.py", line 8402, in groupby
    return DataFrameGroupBy(
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/pandas/core/groupby/groupby.py", line 965, in __init__
    grouper, exclusions, obj = get_grouper(
  File "/opt/miniconda3/envs/llm/lib/python3.10/site-packages/pandas/core/groupby/grouper.py", line 888, in get_grouper
    raise KeyError(gpr)
KeyError: 'metric_name'
```

## 运行环境

- 操作系统：ubuntu 20.04
- Python版本：3.12.0

## 其他信息

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


HLE数据集评测需要配置裁判模型：`judge_model_args`，参考这里：https://evalscope.readthedocs.io/zh-cn/latest/get_started/parameters.html#judge

这个报错信息后续优化一下

@Yunnglin  The same error persists after adding --judge-model-args and install from source/main, from the log seems like nothing changed? 

Could you check the log to see if there are any other error messages? Please provide them if you find any.

No not only warnings related to deprecated `timeout` and `stream` @Yunnglin 

I feel like corrupted `prediction` data, since the same environment, other model have succeeded.  Any advice on how to trace / debug?