Open blozano-tt opened 3 weeks ago
In theory CTest could replace all of these scripts
I made a mistake of looking somewhere I should not have. $ wc -l tests/scripts/*.sh 876 23:47:33 14 tests/scripts/run_build_docs.sh 147 tests/scripts/run_cpp_fd2_tests.sh 30 tests/scripts/run_cpp_unit_tests.sh 26 tests/scripts/run_models.sh 46 tests/scripts/run_moreh_microbenchmark.sh 192 tests/scripts/run_performance.sh 25 tests/scripts/run_pre_post_commit_regressions_fast_dispatch.sh 26 tests/scripts/run_pre_post_commit_regressions_slow_dispatch.sh 113 tests/scripts/run_profiler_regressions.sh 21 tests/scripts/run_python_api_unit_tests.sh 59 tests/scripts/run_python_model_tests.sh 448 tests/scripts/run_tests.sh 61 tests/scripts/run_tools_tests.sh 8 tests/scripts/run_ttnn_examples.sh 21 tests/scripts/run_ttnn_sweeps.sh 36 tests/scripts/set_up_end_to_end_tests_env.sh 90 tests/scripts/tt_bisect.sh 1363 total
Learned recently, that CTest does not work well when the build tree is relocated.
We build on builders, and send artifacts to testers.
I got CTest to work in one instance, but it was nasty.
In theory CTest could replace all of these scripts
I made a mistake of looking somewhere I should not have. $ wc -l tests/scripts/*.sh 876 23:47:33 14 tests/scripts/run_build_docs.sh 147 tests/scripts/run_cpp_fd2_tests.sh 30 tests/scripts/run_cpp_unit_tests.sh 26 tests/scripts/run_models.sh 46 tests/scripts/run_moreh_microbenchmark.sh 192 tests/scripts/run_performance.sh 25 tests/scripts/run_pre_post_commit_regressions_fast_dispatch.sh 26 tests/scripts/run_pre_post_commit_regressions_slow_dispatch.sh 113 tests/scripts/run_profiler_regressions.sh 21 tests/scripts/run_python_api_unit_tests.sh 59 tests/scripts/run_python_model_tests.sh 448 tests/scripts/run_tests.sh 61 tests/scripts/run_tools_tests.sh 8 tests/scripts/run_ttnn_examples.sh 21 tests/scripts/run_ttnn_sweeps.sh 36 tests/scripts/set_up_end_to_end_tests_env.sh 90 tests/scripts/tt_bisect.sh 1363 total