You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Execution tracker prints out unneeded warnings which can only confuse the user. From my understanding this tool should be used only as part of the test infrastructure, so in that sense it doesn't make sense to be active when we are not running tests.
If we want to expose it to the user then clear APIs need to be provided.
Example:
2025-03-04 10:40:34.563 | INFO | forge.compile:compile_main:227 - Compiling module Add
2025-03-04 10:40:34.564 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage init_compile
2025-03-04 10:40:34.564 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage generate_initial_graph
2025-03-04 10:40:34.564 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.071 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.072 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.093 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.116 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.145 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.146 | DEBUG | forge.tvm_to_python:_determine_node_dtype:2149 - Node 'x1' does not have a framework dtype specified. Using TVM generated dtype.
2025-03-04 10:40:36.146 | DEBUG | forge.tvm_to_python:_determine_node_dtype:2149 - Node 'x2' does not have a framework dtype specified. Using TVM generated dtype.
2025-03-04 10:40:36.148 | DEBUG | forge.verify.compare:compare_tensor_to_golden:289 - Tensors match on Framework vs. Forge codegen output 0
2025-03-04 10:40:36.148 | INFO | forge.tvm_to_python:verify_framework_vs_forge_codegen:1955 - Verified python codegen agains framework
2025-03-04 10:40:36.149 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.156 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.156 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage post_initial_graph_pass
2025-03-04 10:40:36.161 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.162 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage optimized_graph
2025-03-04 10:40:36.179 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.185 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.185 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage post_autograd_pass
2025-03-04 10:40:36.191 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.191 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage consteval_graph
2025-03-04 10:40:36.196 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.196 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage pre_lowering_pass
2025-03-04 10:40:36.200 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.200 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage split_graph
2025-03-04 10:40:36.206 | WARNING | forge.execution_tracker:record_execution_phase_and_stage:177 - Unable to find current test
2025-03-04 10:40:36.206 | INFO | forge.compile:forge_compile_from_context:286 - Running compile stage run_mlir_compiler
2025-03-04 10:40:36.208 | INFO | Always - Emitting mlir for function forward
The text was updated successfully, but these errors were encountered:
Execution tracker prints out unneeded warnings which can only confuse the user. From my understanding this tool should be used only as part of the test infrastructure, so in that sense it doesn't make sense to be active when we are not running tests.
If we want to expose it to the user then clear APIs need to be provided.
Example:
The text was updated successfully, but these errors were encountered: