1. 05 Jul, 2020 1 commit
  2. 03 Jul, 2020 14 commits
  3. 02 Jul, 2020 23 commits
  4. 01 Jul, 2020 2 commits
    • Tiger Oakes's avatar
      Remove roboletric runner for some lib tests · 758d01b7
      Tiger Oakes authored
    • MozLando's avatar
      Merge #7510 · 1cba216b
      MozLando authored
      7510: Add firefox profiler marker API to the GeckoEngine r=pocmo a=canova
      Hi all, I'm on the Firefox Profiler team and I was working on the geckoview API for the Firefox and just landed the GeckoView part in [Bug 1624993](https://bugzilla.mozilla.org/show_bug.cgi?id=1624993). I also want to add this API to android-components so we can use that API in the consumers like Fenix. This is still not exactly complete but I wanted to get some early feedback from you. It would be great if you can take a look at it.
      - I added a `ProfilerRuntime` interface and added that interface to `GeckoEngine`. These ProfilerRuntime methods calls the geckoview APIs. I'm not exactly sure about the place. I added it to GeckoEngine class but I can move it to somewhere else too if you think it's not great.
      - Also currently I didn't add any tests and I would like to get your feedback on how to write this as well. This feels like a bit tricky, because when the profiler is not running, these methods are no-op. And currently there is no way to enable profiler from geckoview. It's only possible with[ remote profiling via `about:debugging`](https://profiler.firefox.com/docs/#/./guide-remote-profiling
      ). So I'm not sure what to test here. Maybe if we have some devtools tests in the codebase, I can try to do some things like these.
      Co-authored-by: default avatarNazım Can Altınova <canaltinova@gmail.com>