WebRTC log with higher severity are incorrectly filtered out

What steps will reproduce the problem?
1. Build release version of chrome/libjingle/webrtc from tip-of-tree.
2. Start chrome with webrtc logs enabled (--enable-logging=stderr --v=1 
--vmodule=*libjingle/source/*=3)

What is the expected output? What do you see instead?
It was expected to see WEBRTC_TRACE(kTraceError) logs. But they were not 
printed.

What version of the product are you using? On what operating system?
Tot synced last week on chrome OS (Lucas).

Please provide any additional information below.
In libjingle, higher severity number is more severe. In chromium, lower 
severity number is more severe. In WebRtcVideoEngine::Print(), 
third_party/libjingle/source/talk/media/webrtc/webrtcvideoengine.cc, higher 
severity logs are incorrectly filtered out by the line "if (sev >= log_level_) 
{".

https://code.google.com/p/libjingle/source/browse/trunk/talk/media/webrtc/webrtc
videoengine.cc#1220

Original issue reported on code.google.com by wuchen...@chromium.org on 26 Mar 2013 at 5:12

SteelRiceContainer / libjingle

WebRTC log with higher severity are incorrectly filtered out #427