summaryrefslogtreecommitdiffstats
path: root/test
diff options
context:
space:
mode:
authorMatt Spinler <spinler@us.ibm.com>2018-03-29 08:48:37 -0500
committerMatt Spinler <spinler@us.ibm.com>2018-04-12 13:58:33 -0500
commit3d2b0d62ed1567ffba53ffb44d0a8617869ea08c (patch)
tree4afd5be16485ab42865a2c05d40edf1b19c0d736 /test
parent3aa931d594a38a26176abce7e809e535bfe9f668 (diff)
downloadphosphor-led-manager-3d2b0d62ed1567ffba53ffb44d0a8617869ea08c.tar.gz
phosphor-led-manager-3d2b0d62ed1567ffba53ffb44d0a8617869ea08c.zip
Move down error entry trace
It's possible that multiple services can provide the /xyz/openbmc_project/logging paths, which means the interfaces added handler can get multiple callbacks for a single error. That being the case, move down the trace that shows the new error log object path until after the code checks that the association interface is present, as that interface will only be present on one object. Another option would have been to remove the trace completely, but it is fairly useful for debug. Change-Id: I98659562ef024455762110e20109bf3079b96cbe Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud