Closed uduse closed 2 years ago
Hey @uduse! Sorry for the slow reply. I looked into this and the bug is in the logging setup code in compiler_gym/leaderboard/llvm_instcount.py
:
Changing the line:
- logger.setLevel(logging.DEBUG)
+ logger.setLevel(logging.WARNING)
Prevented those debugging logs from being printed to stdout. Of course, it also prevents the logging output from being written to file. I'll see if there's a proper fix down the road. In the meantime, patches welcome!
Cheers, Chris
Thanks for the reply. I have no idea how I missed that line. I looked at that file at least ten times. Need to eat more ð and ðŦ ðĪĢ
Also do you have any plan to change llvm_instcount.py
in the near future?
Hah, no worries! I'll keep this open for now as it is definitely a bug and might be an easy fix for someone looking to contribute.
Also do you have any plan to change llvm_instcount.py in the near future?
We have discussed that, but tbh I don't think its on anyone's near term roadmap. There's a few things that it could do better, like parallel evaluation for single-threaded searches, better support for logging agent progress, etc. Why do you ask?
Cheers, Chris
I'm working a better evaluation script for my research. If you don't have a plan for now, maybe I'll do a PR later. No promise at all though ðĪŠ
Oh nice! I look forward to it if/when ð
Cheers, Chris
â Questions and Help
It seems these prints are
DEBUG
level but I couldn't find the correct command line flags to turn these off. Any ideas? ð