tests: anchor the inheritance order check on the call, not the definition
source.index("_resolve_inherited_extra_args(") matched the function
definition, which always precedes the endpoint, so the ordering
assertion was vacuously true. Anchoring on "= _resolve_inherited_
extra_args(" pins the first call site inside the load endpoint (line
4505), which is the statement whose position relative to the GGUF
branch the test is meant to guard. 32 tests pass.
This commit is contained in:
parent
fd306b0362
commit
6a3db3b9e0
1 changed files with 1 additions and 1 deletions
|
|
@ -730,7 +730,7 @@ class TestLoadHubDownloadExclusion:
|
|||
|
||||
# Pass-through inheritance runs before the GGUF branch, so a carried
|
||||
# --no-mmproj shapes the hub guard's companion requirement.
|
||||
assert source.index("_resolve_inherited_extra_args(") < source.index("if config.is_gguf:")
|
||||
assert source.index("= _resolve_inherited_extra_args(") < source.index("if config.is_gguf:")
|
||||
assert (
|
||||
gguf_branch.index("enter_context(gguf_load_in_flight")
|
||||
< gguf_branch.index("_hub_download_blocks_gguf_load")
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue