On Friday, June 5, 2015 at 8:23:53 AM UTC-7, ISHIKAWA,chiaki wrote: > After coping with voluminous messages in C-C TB |make mozmill| test > suite log [much smaller volume than full FF logs], > I think we should have NS_INFORMATION() macro that > prints out an information for someone who is developing code and > just wants to know how the code is doing.
I suppose we could add yet another macro, but really this sounds like a use case for: MOZ_LOG(myModule, LogLevel::Info, "Dev message!"); which could then be enabled with something like: |NSPR_MODULES="myModule:3" ./mach run| It might be useful to eventually add a |MOZ_LOG_IF| to make things easier. > 1576 [10262] WARNING: '!mMainThread', file > /REF-COMM-CENTRAL/comm-central/mozilla/xpcom/threads/nsThreadManager.cpp, > line We're working on this in bug 1171716, it's related to cycle collection on shutdown. > Anyway, I agree that we should simply try to attack the top entries > first to figure out whether they are indication of genuine issues/bugs, etc. Yes! Please file blocking bugs for the top c-c entries against bug 765224. > Eventually we could cut down the number to manageable size. > (At near the beginning of 2013, the list became only about a dozen items > long, but started to grow again. In a sense it reflects the desire of > code authors to catch strange conditions, but I agree we must keep on > looking at the logs and do something about the top offenders in the log > list.) It might be nice to create a very simple start/stop test that just makes sure there are no warnings so that we can avoid regressing that in the future. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
