Histogram DBus.RejectedSignalCount is unmapped |
||
Issue descriptionThe histogram 'DBus.RejectedSignalCount' is present in Chromium source code but does not appear in histograms.xml. This means that data is collected for the histogram but nothing useful is done with it. The histogram was defined in dbus/object_proxy.cc at line 506. https://cs.chromium.org/chromium/src/dbus/object_proxy.cc?l=506 It may have moved by the time you read this. Please remove the histogram 'DBus.RejectedSignalCount' from the source code. If it was very recently added, it may be worth adding it to histograms.xml instead, but probably not. This bug was automatically assigned based on git blame information. If you are not the correct assignee for this bug, please delete the histogram anyway.
,
Apr 25 2017
,
Apr 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/72254d5183b29735f1cfe999cc7926f55c4dedb0 commit 72254d5183b29735f1cfe999cc7926f55c4dedb0 Author: hashimoto <hashimoto@chromium.org> Date: Tue Apr 25 07:13:31 2017 dbus: Stop collecting DBus.RejectedSignalCount histogram Also, use shorter timeout for SignalSenderVerificationTest.TestSignalRejected which was disabled because of its slowness. BUG= 407063 , 643537 TEST=dbus_unittests Review-Url: https://codereview.chromium.org/2837943004 Cr-Commit-Position: refs/heads/master@{#466912} [modify] https://crrev.com/72254d5183b29735f1cfe999cc7926f55c4dedb0/dbus/object_proxy.cc [modify] https://crrev.com/72254d5183b29735f1cfe999cc7926f55c4dedb0/dbus/signal_sender_verification_unittest.cc
,
Apr 25 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by ricea@chromium.org
, Apr 21 2017Owner: hashimoto@chromium.org