Commits on Source (6)
-
Derek Foreman authored
We have a few places where we log messages only the first time they occur. Provide a log throttling implementation so we don't have to open code this in all the places that need it. Instead of just logging a single time, allow some finer control. We allow logging of a specified number of events. Additionally, we have an optional timeout after which the event count is reset so we can log at most N events in M ms. The first new event printed after the timeout expires will also include a count of suppressed events. Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
8e661b3c -
Derek Foreman authored
Ideally we'd like to see this more than just a single time, but we'd also like to prevent it from triggering endlessly. Let's also make this happen per output. While we're here, use the word "abnormal" instead of "insane" Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
f9b57c52 -
Derek Foreman authored
The current code only prints this once, and this is a probably a sensible thing to do, as a clock read failure is probably not a condition that will correct itself. Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
a82cb251 -
Derek Foreman authored
Mimic the existing behaviour of logging 5 times, with no reset, but change it so it's per device instead of using a static variable. Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
805c7c48 -
Derek Foreman authored
Mimic the existing behaviour of logging once, but make it once per output instead of per run. Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
6428fd13 -
Derek Foreman authored
Copy the existing behaviour with the new paced logging mechanism. Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
771bd8ac