mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-09 03:18:44 +00:00
test(e2e): mark known pricing-leak isolation test xfail(strict)
test_custom_pricing_is_isolated_from_sibling_deployment documents a real proxy gap (a deployment's custom per-token pricing leaks into the shared cost map for sibling deployments of the same underlying model) and was left unconditionally failing, which pollutes the suite's pass/fail signal. Mark it xfail(strict=True) so the suite stays green while the leak persists and turns into a failure the moment isolation is fixed, prompting the marker's removal.
This commit is contained in:
parent
87d1f5b41c
commit
d80c4f49a4
1 changed files with 9 additions and 2 deletions
|
|
@ -10,8 +10,9 @@ back here from the same config file. Three behaviors are checked independently:
|
|||
- reporting: /model/info surfaces those rates for the model
|
||||
- isolation: gemini-2.5-flash shares the same underlying gemini/gemini-2.5-flash
|
||||
but sets no override, so it must keep its own price; an override that leaks into
|
||||
the shared cost map misprices it. This currently fails on a real gap and is left
|
||||
failing rather than weakened to pass.
|
||||
the shared cost map misprices it. This fails on a real proxy gap today, so it is
|
||||
marked xfail(strict=True): the suite stays green while the leak persists and
|
||||
flips to a failure the moment isolation is fixed and the marker should be removed.
|
||||
"""
|
||||
|
||||
import time
|
||||
|
|
@ -191,6 +192,12 @@ def test_model_info_reports_custom_pricing(client: PassthroughClient) -> None:
|
|||
)
|
||||
|
||||
|
||||
@pytest.mark.xfail(
|
||||
strict=True,
|
||||
reason="known proxy bug: a deployment's custom per-token pricing leaks into the "
|
||||
"shared cost map for sibling deployments of the same underlying model; remove "
|
||||
"this marker once isolation is fixed",
|
||||
)
|
||||
def test_custom_pricing_is_isolated_from_sibling_deployment(
|
||||
client: PassthroughClient,
|
||||
) -> None:
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue