Closed
Bug 1432598
Opened 6 years ago
Closed 6 years ago
First-run screen displayed during Android browser tests
Categories
(Firefox for Android Graveyard :: Testing, enhancement, P1)
Firefox for Android Graveyard
Testing
Tracking
(firefox60 fixed)
RESOLVED
FIXED
Firefox 60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 file)
1.00 KB,
patch
|
snorp
:
review+
|
Details | Diff | Splinter Review |
When Android mochitest and reftest tests are run on a new install, Firefox displays the first-run screen, and generally continues to display that for the duration of the test. That's generally harmless, in that it doesn't appear to affect test results or performance. However, in local runs, it's nice to see mochitests running; and in continuous integration, failure screenshots can be useful if content is actually changing over time!
Assignee | ||
Comment 1•6 years ago
|
||
Simple to implement and does no harm on try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=d2eab28081deead4330e7b756f752b3ca47eaf0b
Attachment #8944848 -
Flags: review?(snorp)
Assignee | ||
Updated•6 years ago
|
Priority: -- → P1
Attachment #8944848 -
Flags: review?(snorp) → review+
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/b5948a2c4fc2 Do not show first-run screens during android tests; r=snorp
Comment 3•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b5948a2c4fc2
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
Comment 4•6 years ago
|
||
This slightly improved one of our baselines: == Change summary for alert #11308 (as of Thu, 25 Jan 2018 16:59:55 GMT) == Improvements: 3% Resident Memory android-4-2-x86 opt 193,879,158.67 -> 188,638,498.75 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=11308
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•