Skip to content

Commit

Permalink
fix example with remove_parameter_value_pairs_ranges()
Browse files Browse the repository at this point in the history
  • Loading branch information
SimeonEhrig committed Sep 23, 2024
1 parent d94b57f commit 5698733
Showing 1 changed file with 11 additions and 6 deletions.
17 changes: 11 additions & 6 deletions example/example.py
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@
check_parameter_value_pair_in_combination_list,
check_unexpected_parameter_value_pair_in_combination_list,
remove_parameter_value_pairs,
remove_parameter_value_pairs_ranges,
)
from bashi.results import get_expected_bashi_parameter_value_pairs
from bashi.types import (
Expand Down Expand Up @@ -154,25 +155,29 @@ def verify(combination_list: CombinationList, param_value_matrix: ParameterValue
max_supported_nvcc_gcc_version = max(comb.host for comb in NVCC_GCC_MAX_VERSION).major
max_supported_nvcc_clang_version = max(comb.host for comb in NVCC_CLANG_MAX_VERSION).major
for cpu_backend in cpu_backends:
remove_parameter_value_pairs(
remove_parameter_value_pairs_ranges(
expected_param_val_tuple,
unexpected_param_val_tuple,
parameter1=HOST_COMPILER,
value_name1=GCC,
value_version1=f"<={max_supported_nvcc_gcc_version}",
value_min_version1=max_supported_nvcc_gcc_version,
value_min_version1_inclusive=False,
parameter2=cpu_backend,
value_name2=cpu_backend,
value_version2=OFF,
value_min_version2=OFF,
value_max_version2=OFF,
)
remove_parameter_value_pairs(
remove_parameter_value_pairs_ranges(
expected_param_val_tuple,
unexpected_param_val_tuple,
parameter1=HOST_COMPILER,
value_name1=CLANG,
value_version1=f"<={max_supported_nvcc_clang_version}",
value_min_version1=max_supported_nvcc_clang_version,
value_min_version1_inclusive=False,
parameter2=cpu_backend,
value_name2=cpu_backend,
value_version2=OFF,
value_min_version2=OFF,
value_max_version2=OFF,
)

def all_cpu_backends_are(expected_state: pkv.Version, combination: Combination) -> bool:
Expand Down

0 comments on commit 5698733

Please sign in to comment.