LMCache / LMCache/lmcache-tests
ValueError: not enough values to unpack (expected 4, got 2)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Since there is no powerful GPU, we have to run the End2End test with a samll model Qwen/Qwen2-1.5B. LMcache could start successfully. We get the error when sending requests to server.
The error from current screen:
And the error from /tmp/root-8000-stdout.log
(VllmWorkerProcess pid=73509) ERROR 11-20 22:14:12 multiproc_worker_utils.py:233] _, _, num_heads, head_size = kv_cache[0].shape
(VllmWorkerProcess pid=73509) ERROR 11-20 22:14:12 multiproc_worker_utils.py:233] ValueError: not enough values to unpack (expected 4, got 2)
env:
- OS: Ubuntu 22.04.5 LTS
- vllm: v0.6.2 (pip install vllm==0.6.2)
- LMcache: v0.1.3-alpha (installed from source)
- lmcache-vllm: v0.6.2.2 (installed from source)
- GPU: Tesla T4 (16GB) x 2
To Reproduce
Steps to reproduce the behavior:
- Set to use
Qwen/Qwen2-1.5Bby changingtests/tests.py.def test_lmcache_local_cpu(model = "Qwen/Qwen2-1.5B") -> pd.DataFrame: - python3 main.py tests/tests.py -f test_lmcache_local_cpu -o outputs/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by changing the model in tests/tests.py and running python3 main.py tests/tests.py -f test_lmcache_local_cpu -o outputs/. Read the /tmp/root-8000-stdout.log traceback around multiproc_worker_utils.py:233 and inspect the kv_cache[0].shape assumption. Done means the End2End test completes without the unpacking error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100