User-provided session logging function is not used for every log #20680
Labels
ep:CUDA
issues related to the CUDA execution provider
ep:DML
issues related to the DirectML execution provider
ep:TensorRT
issues related to TensorRT execution provider
platform:windows
issues related to the Windows platform
Describe the issue
Since ORT 1.17, we have the ability to assign a logging function to the session options.
However, the feature seems to be incomplete as it only affects some logs where it should affect all of them.
To reproduce
Just create a session with a user-defined logging function. While the session is created, you'll notice a lot of logs to the console (the environment's default logger), while some others are passed to the session logging function.
Here's an (incomplete) example:
Urgency
Not urgent.
Platform
Windows
OS Version
Windows 11 23H2
ONNX Runtime Installation
Built from Source
ONNX Runtime Version or Commit ID
1.17.3 and 1.18.0 RC
ONNX Runtime API
C++
Architecture
X64
Execution Provider
Default CPU, CUDA, DirectML, TensorRT
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: