Hi all, I am sending this e-mail to start a discussion about current log mechanism. As you might know that we have different ways to collect logs, most kinds of logs need extra actions to enable them since performance issues. With more devices and users, the issues reported may not always come with solid STR (steps to reproduce). Some automation tests (such as MTBF and Orangutan Test) will not always have STR. Worse than that, the logs collected during testing contain no clues for resolving issues most of the time.
Currently, the information we can get by "adb logcat" command is about WiFi. We'll need to use special methods to trigger RIL and it's not known by public. For Gaia logs, we'll need to reach the developers to know how to trigger its logger, or there's no logger due to performance concern. Within offline discuss with Tim, a centralized log mechanism control by the system app could be a solution. Or we can implement the log server inside gecko, direct all configuration to gecko, and let gecko decide when to drop logs. More thoughts are welcome. Best Regards, Al -- Al Tsai Senior QA Engineer, MoCo Taiwan Tel: +886-2-87861100 ext.358
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
