[Good First Issue]: Improve logging for OpenVINO torch.compile feature
#33,116 opened on Dec 3, 2025
Repository metrics
- Stars
- (10,286 stars)
- PR merge metrics
- (Avg merge 14d 3h) (305 merged PRs in 30d)
Description
Context
Currently when developers are using torch.compile feature in openvino for their Pytorch models even with debug logging swtiched on they aren't able to see a lot of logs being printed for OpenVINO backend. So, the users are not able to understand if they model is running on OpenVINO or Native Pytorch.
What needs to be done?
Need to add verbose logging for OpenVINO Torch.Compile feature. The user needs to be able to tell if OpenVINO is being used and if so what are the subgraphs being delegated to openvino. Also, the user needs to be able to know when a model has fallen back to Native Pytorch instead of using OpenVINO.
Resources
Contact points
@suryasidd @ynimmaga @cavusmustafa
AI notice - Important!
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.
Ticket
No response