There was one time that all the memory reports are not fetched correctly. all cc files are empty. I just opened this bug for tracking. There might be nothing we can look into.

not exactly blocker of MTBF, but it might make the time cost of MTBF goes up a little bit.

Walter, is this still an issue for you? If so can you provide further details? In particular: were the files moved from the device the host machine, and if so were they empty on the host? Also did you see any error messages from |get_about_memory.py|?

I didn't run it for a long time. The log is from mtbf driver, which include libraries&functions from get_about_memory.py in Jenkins environment. I think they are empty on the host. As I told, since no one was taking care for these bugs, I didn't run it for quite a long time. We didn't have the resource to just create bugs and wait here. We continue without using memory report. If someone could promise that all this kind of issues can be investigated. We will try to see how we can cooperate on this thing.

Firefox OS is not being worked on