Lines Matching full:ongoing
23 // Logs fall into one of two categories: "initial logs," and "ongoing logs."
31 // minimum) how often additional ongoing logs should be sent.
33 // After the above initial log, a series of ongoing logs will be transmitted.
34 // The first ongoing log actually begins to accumulate information stating when
40 // periods without any (ongoing) log transmissions. Ongoing logs typically
43 // ongoing log is closed out, a call is made to gather memory statistics. Those
50 // When the browser shuts down, there will typically be a fragment of an ongoing
55 // ongoing log is then stored persistently as a string in the PrefServices, for
63 // the ongoing log (which didn't yet get closed, because there was never even a
65 // situation, where a loss of connection prevented an ongoing log from being
120 // ongoing logs from previous sessions should be transmitted. All such logs
121 // will be transmitted before exiting this state, and proceeding with ongoing
136 // initial log, or an ongoing log). An addition, any log that is currently
271 // The number of ongoing logs we're willing to save persistently, and hope to
868 current_log_->set_hardware_class(hardware_class_); // Adds to ongoing logs.
