[Main2Main] Upgrade vllm commit to releases/v0.14.0 (#5911)
### What this PR does / why we need it?
Upgrade vllm commit to releases/v0.14.0
- Re-open cases in `tests/e2e/singlecard/pooling/test_scoring.py`, since
the errors before have been fixed by
https://github.com/vllm-project/vllm/pull/32243
### Does this PR introduce _any_ user-facing change?
### How was this patch tested?
- vLLM version: v0.13.0
- vLLM main:
11b6af5280
Signed-off-by: wjunLu <wjunlu217@gmail.com>
This commit is contained in:
@@ -5,8 +5,6 @@ import torch
|
||||
import torch.nn.functional as F
|
||||
from modelscope import snapshot_download # type: ignore[import-untyped]
|
||||
|
||||
from vllm_ascend.utils import vllm_version_is
|
||||
|
||||
from tests.e2e.conftest import HfRunner, VllmRunner
|
||||
|
||||
CROSS_ENCODER_MODELS = [
|
||||
@@ -35,10 +33,6 @@ DTYPE = "half"
|
||||
def model_name(request):
|
||||
yield snapshot_download(request.param)
|
||||
|
||||
@pytest.mark.skipif(
|
||||
not vllm_version_is('0.13.0'),
|
||||
reason="vLLM PR-32148 changed the behavior of cross scoring",
|
||||
)
|
||||
def test_cross_encoder_score_1_to_1(model_name):
|
||||
text_pair = [TEXTS_1[0], TEXTS_2[0]]
|
||||
|
||||
@@ -58,10 +52,6 @@ def test_cross_encoder_score_1_to_1(model_name):
|
||||
assert hf_outputs[0] == pytest.approx(vllm_outputs[0], rel=0.01)
|
||||
|
||||
|
||||
@pytest.mark.skipif(
|
||||
not vllm_version_is('0.13.0'),
|
||||
reason="vLLM PR-32148 changed the behavior of cross scoring",
|
||||
)
|
||||
def test_cross_encoder_score_1_to_N(model_name):
|
||||
text_pairs = [
|
||||
[TEXTS_1[0], TEXTS_2[0]],
|
||||
@@ -85,10 +75,6 @@ def test_cross_encoder_score_1_to_N(model_name):
|
||||
assert hf_outputs[1] == pytest.approx(vllm_outputs[1], rel=0.01)
|
||||
|
||||
|
||||
@pytest.mark.skipif(
|
||||
not vllm_version_is('0.13.0'),
|
||||
reason="vLLM PR-32148 changed the behavior of cross scoring",
|
||||
)
|
||||
def test_cross_encoder_score_N_to_N(model_name):
|
||||
text_pairs = [
|
||||
[TEXTS_1[0], TEXTS_2[0]],
|
||||
|
||||
Reference in New Issue
Block a user