[QST]Testing Problem. #674
Description
16 tests of 132 cpp tests failed when I test the project build from the source of the newest version.
Start 107: MPS_PARSER_TEST 107/132 Test #107: MPS_PARSER_TEST ............................................................................***Failed 0.01 sec Start 108: ROUTING_TEST 108/132 Test #108: ROUTING_TEST ............................................................................... Passed 375.15 sec Start 109: ROUTING_GES_TEST 109/132 Test #109: ROUTING_GES_TEST ........................................................................... Passed 21.45 sec Start 110: VEHICLE_ORDER_TEST 110/132 Test #110: VEHICLE_ORDER_TEST ......................................................................... Passed 67.23 sec Start 111: VEHICLE_TYPES_TEST 111/132 Test #111: VEHICLE_TYPES_TEST ......................................................................... Passed 20.37 sec Start 112: OBJECTIVE_FUNCTION_TEST 112/132 Test #112: OBJECTIVE_FUNCTION_TEST .................................................................... Passed 142.19 sec Start 113: RETAIL_L1TEST 113/132 Test #113: RETAIL_L1TEST ..............................................................................***Failed 717.58 sec Start 114: ROUTING_L1TEST 114/132 Test #114: ROUTING_L1TEST .............................................................................***Failed 15.04 sec Start 115: ROUTING_UNIT_TEST 115/132 Test #115: ROUTING_UNIT_TEST .......................................................................... Passed 165.59 sec Start 116: WAYPOINT_MATRIXTEST 116/132 Test #116: WAYPOINT_MATRIXTEST ........................................................................***Failed 0.25 sec Start 117: MIP_TEST 117/132 Test #117: MIP_TEST ...................................................................................***Failed 0.06 sec Start 118: PROBLEM_TEST 118/132 Test #118: PROBLEM_TEST ............................................................................... Passed 0.37 sec Start 119: ELIM_VAR_REMAP_TEST 119/132 Test #119: ELIM_VAR_REMAP_TEST ........................................................................***Failed 0.06 sec Start 120: STANDARDIZATION_TEST 120/132 Test #120: STANDARDIZATION_TEST .......................................................................***Failed 0.06 sec Start 121: MULTI_PROBE_TEST 121/132 Test #121: MULTI_PROBE_TEST ...........................................................................***Failed 0.25 sec Start 122: INCUMBENT_CALLBACK_TEST 122/132 Test #122: INCUMBENT_CALLBACK_TEST ....................................................................***Failed 0.06 sec Start 123: DOC_EXAMPLE_TEST 123/132 Test #123: DOC_EXAMPLE_TEST ........................................................................... Passed 0.48 sec Start 124: UNIT_TEST 124/132 Test #124: UNIT_TEST ..................................................................................***Failed 10.47 sec Start 125: EMPTY_FIXED_PROBLEMS_TEST 125/132 Test #125: EMPTY_FIXED_PROBLEMS_TEST ..................................................................***Failed 0.12 sec Start 126: PRESOLVE_TEST 126/132 Test #126: PRESOLVE_TEST ..............................................................................***Failed 0.06 sec Start 127: MIP_TERMINATION_STATUS_TEST 127/132 Test #127: MIP_TERMINATION_STATUS_TEST ................................................................***Failed 0.06 sec Start 128: LP_UNIT_TEST 128/132 Test #128: LP_UNIT_TEST ...............................................................................***Failed 0.25 sec Start 129: PDLP_TEST 129/132 Test #129: PDLP_TEST ..................................................................................***Failed 0.35 sec Start 130: C_API_TEST 130/132 Test #130: C_API_TEST .................................................................................***Failed 0.36 sec Start 131: DUAL_SIMPLEX_TEST 131/132 Test #131: DUAL_SIMPLEX_TEST .......................................................................... Passed 0.38 sec Start 132: CLI_TEST 132/132 Test #132: CLI_TEST ................................................................................... Passed 7.62 sec
main failed question falls into 3 types:
type 1:(open mps fail)
`C++ exception with description "{"MPS_PARSER_ERROR_TYPE": "ValidationError", "msg": "Error opening MPS file! Given path: ./datasets/mip/fixed-problem.mps"}" thrown in the test body.
[ FAILED ] mip_solve.fixed_problem_test (0 ms)
[ RUN ] mip_solve.fixed_problem_infeasible_test
unknown file: Failure
C++ exception with description "{"MPS_PARSER_ERROR_TYPE": "ValidationError", "msg": "Error opening MPS file! Given path: ./datasets/mip/fixed-problem-infeas.mps"}" thrown in the test body.
[ FAILED ] mip_solve.fixed_problem_infeasible_test (0 ms)
[ RUN ] mip_solve.empty_problem_test
unknown file: Failure
C++ exception with description "{"MPS_PARSER_ERROR_TYPE": "ValidationError", "msg": "Error opening MPS file! Given path: ./datasets/mip/empty-problem-obj.mps"}" thrown in the test body.
[ FAILED ] mip_solve.empty_problem_test (0 ms)
[ RUN ] mip_solve.empty_problem_with_objective_test
unknown file: Failure
C++ exception with description "{"MPS_PARSER_ERROR_TYPE": "ValidationError", "msg": "Error opening MPS file! Given path: ./datasets/mip/empty-problem-objective-vars.mps"}" thrown in the test body.
[ FAILED ] mip_solve.empty_problem_with_objective_test (0 ms)
[ RUN ] mip_solve.empty_max_problem_with_objective_test
unknown file: Failure
C++ exception with description "{"MPS_PARSER_ERROR_TYPE": "ValidationError", "msg": "Error opening MPS file! Given path: ./datasets/mip/empty-max-problem-objective-vars.mps"}" thrown in the test body.
[ FAILED ] mip_solve.empty_max_problem_with_objective_test (0 ms)
[ RUN ] mip_solve.mip_presolved_to_lp
unknown file: Failure
C++ exception with description "{"MPS_PARSER_ERROR_TYPE": "ValidationError", "msg": "Error opening MPS file! Given path: ./datasets/mip/mip-presolved-to-lp.mps"}" thrown in the test body.`
type 2:
`
C++ exception with description "{"CUOPT_ERROR_TYPE": "ValidationError", "msg": "Offsets input cannot be null."}" thrown in SetUp().
[ FAILED ] test_waypoint_matrix/float_waypoint_matrix_cost_matrix_test_t.compute_cost_matrix/0, where GetParam() = 120-byte object <00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00> (0 ms)`
type 3:
`
Parameterized test suite regression_routing_test_pickup_t is defined via TEST_P, but never instantiated. None of the test cases will run. Either no INSTANTIATE_TEST_SUITE_P is provided or the only ones provided expand to nothing.
Ideally, TEST_P definitions should only ever be included as part of binaries that intend to use them. (As opposed to, for example, being placed in a library that may be linked in to get other utilities.)
To suppress this error for this test suite, insert the following line (in a non-header) in the namespace it is defined in:
GTEST_ALLOW_UNINSTANTIATED_PARAMETERIZED_TEST(regression_routing_test_pickup_t);`
cuda-toolkit:13.2.0
cmake:4.2.0
I remove the python install steps from the build.sh when execute the build.sh
Are there any wrong steps in installation process will cause the issue mentioned above?