Silence debug messages from Qt #586

Merged
merged 1 commit into from Nov 9, 2013

Projects

None yet

3 participants

@jferris
Member
jferris commented Nov 7, 2013
  • 99% of the messages we see are useless
  • Debug output is driving OS X users nuts
@jferris
Member
jferris commented Nov 7, 2013

This should fix #260, #483, #485, and #581.

@jferris jferris Silence debug messages from Qt
* 99% of the messages we see are useless
* Debug output is driving OS X users nuts
cf2c42d
@jferris jferris merged commit cf2c42d into master Nov 9, 2013
@jferris jferris deleted the jf-silence-debug-messages branch Nov 9, 2013
@wbyoung
wbyoung commented Dec 10, 2013

I seem to still be getting CoreText performance note... messages with 1.1.0. Anything I can check to see why?

@jferris
Member
jferris commented Dec 11, 2013

Unfortunately, it seems as though this only silences messages that come from Qt itself. Qt's code causes several warnings from OS X libraries, including CoreText, and those warnings go directly to STDOUT. I'm still working on a way to generally silence those warnings.

@wbyoung
wbyoung commented Dec 11, 2013

Great, thanks!

@miketrewartha

@wbyoung I think it's an issue with your Qt version, not your capybara-webkit version. If you're using Homebrew to manage things, try this: brew uninstall qt, then run qmake. If you don't get an error about how qmake can't be found, then you've most likely got an install of Qt that's living elsewhere and capybara-webkit might be using it. I had an uninstall script for it in my /Developer/Tools directory. Run that using sudo python <script_name>. Finally, regardless of whether or not the qmake failed, run brew update && brew install qt and give your specs another shot. That might clear up the CoreText performance note messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment