[CI] 【Hackathon 9th Sprint No.38】NO.38 功能模块单测补充 by xunyoyo · Pull Request #5060 · PaddlePaddle/FastDeploy (original) (raw)

This file contains tests for the global scheduler, including request handling, load accounting, and response management.

Motivation

NO.38 功能模块 fastdeploy/scheduler/global_scheduler.py 单测补充

Modifications

new dir and add tests/scheduler/test_global_scheduler.py

Usage or Command

tests/scheduler/test_global_scheduler.py:

python -m coverage run -m unittest tests.scheduler.test_global_scheduler
&& python -m coverage report -m --include='fastdeploy/scheduler/global_scheduler.py'

Accuracy Tests

tests/scheduler/test_global_scheduler.py:

Name Stmts Miss Cover Missing

fastdeploy/scheduler/global_scheduler.py 369 62 83% 200-202, 214-215, 231-241, 332, 424-429, 440-441, 499-502, 511, 520, 532-533, 542-543, 556-561, 576, 601, 652, 681-682, 699-730, 774-775

TOTAL 369 62 83%

Checklist

• Add at least a tag in the PR title.
  • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
  • You can add new tags based on the PR content, but the semantics must be clear.
• Format your code, run pre-commit before commit.
• Add unit tests. Please write the reason in this PR if no unit tests.
• Provide accuracy results.
• If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.