| commit | 117da80c79c8f23a63bea188254c328f7b957a35 | |
| author | Michael Comella <michael.l.comella@gmail.com> | |
| Fri, 3 Sep 2021 21:43:46 +0000 (3 14:43 -0700) | ||
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | |
| Tue, 7 Sep 2021 21:53:43 +0000 (7 21:53 +0000) | ||
| tree | 43e16daeadd145dcd04f714e945d9c0e429e8d35 | treesnapshot (tar.gz zip) |
| parent | b21aa1b68cb9cc2fcc91a954269214a3090ad84c | commitdiff |
[fenix] For https://github.com/mozilla-mobile/fenix/issues/21138: re-enable excessive resource use test.
This test wasn't running in CI
https://github.com/mozilla-mobile/fenix/issues/20386 so we changed the
CI configuration so that it will. However, the test was then failing so
this is the revision that unignores the test.
I wonder if componentInit count is useful - it seems like it'd cause
more false positives than not - but I figure we can leave it in and see
how it goes.
This test wasn't running in CI
https://github.com/mozilla-mobile/fenix/issues/20386 so we changed the
CI configuration so that it will. However, the test was then failing so
this is the revision that unignores the test.
I wonder if componentInit count is useful - it seems like it'd cause
more false positives than not - but I figure we can leave it in and see
how it goes.
| mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/perf/StartupExcessiveResourceUseTest.kt | diffblobblamehistory |