Consider Preset Try Options for GeckoView
Categories
(Developer Infrastructure :: Try, enhancement)
Tracking
(firefox126 fixed)
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: olivia, Assigned: hneiva)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Now with the monorepo, other areas of android have ./mach try --presets
of fenix
firefox-android
, android-components
and focus
. It would be nice to have a similar set of default preset tests for geckoview
that cover the basic junit and other core tests.
Reporter | ||
Comment 1•11 months ago
|
||
(This bug should likely move to a tooling component, but need a list of tests for the preset first.)
Reporter | ||
Comment 2•11 months ago
•
|
||
Hi, I'm not sure of the right component this should go to, but GeckoView developers would like a preset of geckoview
to use with ./mach try --preset geckoview
that runs the following tests to help standardize test selection:
[
"source-test-mozlint-android-lints",
"source-test-mozlint-eslint",
"source-test-mozlint-rejected-words",
"source-test-mozlint-file-perm",
"source-test-mozlint-file-whitespace",
"test-android-em-7.0-x86_64-qr/opt-geckoview-test-verify",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-junit-nofis",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-plain-5",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-plain-5",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-media-2",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-media-1",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-test-verify-nofis",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-xpcshell-2",
"test-android-em-7.0-x86_64-qr/opt-geckoview-test-verify-nofis",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-cppunittest-1proc",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-plain-3",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-plain-4",
"test-android-em-7.0-x86_64-qr/debug-geckoview-xpcshell-1",
"test-android-em-7.0-x86_64-qr/opt-geckoview-cppunittest-1proc",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-plain-1",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-plain-gpu",
"test-android-em-7.0-x86_64-qr/opt-geckoview-junit-nofis-ship",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-plain-4",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-test-verify",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-plain-2",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-junit-fis",
"test-android-em-7.0-x86_64-qr/opt-geckoview-junit-nofis",
"test-android-em-7.0-x86_64-qr/opt-geckoview-gtest-1proc",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-xpcshell-1",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-junit-nofis-ship",
"test-android-em-7.0-x86_64-qr/opt-geckoview-junit-fis",
"test-android-em-7.0-x86_64-qr/opt-geckoview-junit",
"test-android-em-7.0-x86_64-qr/debug-geckoview-xpcshell-2",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-plain-1",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-junit",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-mochitest-plain-3",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-plain-2",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-plain-gpu",
"test-android-em-7.0-x86_64-qr/debug-isolated-process-geckoview-gtest-1proc",
"test-android-em-7.0-x86_64-qr/opt-geckoview-mochitest-media"
]
Comment 3•11 months ago
|
||
Good news! It should be a matter of updating tools/tryselect/try_presets.yml
[1] just like we did in bug 1882616. I'm happy to help reviewing if the change is urgent 🙂
Assignee | ||
Comment 4•11 months ago
|
||
Updated•11 months ago
|
Assignee | ||
Comment 5•11 months ago
|
||
:olivia can you please double check if these are the tasks required to run under the new profile?
Reporter | ||
Comment 6•11 months ago
|
||
Awesome, thank you!
- Could you move X tests (xpcshell) to
Android 7.0 x86-64 WebRender opt
andAndroid 7.0 x86-64 WebRender debug-isolated-process
? (It is okay there, but might be nice to avoid a build, if we can.) - Could we skip
Linux 18.04 x64 opt
andWindows 11 x64 opt
items too? - It would probably be nice to avoid some of the builds on
Android 5.0 x86-64 opt
,Android 5.0 x86-64 debug
,Android 5.0 x86-64 debug-isolated-process
, andAndroid 7.0 x86-64 WebRender debug
for a time saving opportunity. I'm not sure what is typical though for a general test though and a best practice, what do you recommend?
I'll confirm this with other GeckoView developers too, thanks!
:owlish, :calu, anything you'd like to add or change or recommend?
![]() |
||
Comment 7•11 months ago
|
||
Just checking: No reftests or web-platform-tests are desired with this preset?
Reporter | ||
Comment 8•11 months ago
|
||
Just checking: No reftests or web-platform-tests are desired with this preset?
There was some concern with GeckoView reviewers and time to run WPT tests. If you think it would be a best practice and not a huge time/cost concern, then it could be nice to add.
I personally usually run WPT tests for certain changes too. Not sure what the right balance of test completeness and time/cost we should be aiming for.
![]() |
||
Comment 9•11 months ago
|
||
There's probably no "right" answer. I just wanted to check those tests weren't being accidentally overlooked.
Assignee | ||
Comment 10•11 months ago
|
||
:olivia
Could you move X tests (xpcshell) to Android 7.0 x86-64 WebRender opt and Android 7.0 x86-64 WebRender debug-isolated-process? (It is okay there, but might be nice to avoid a build, if we can.)
I'll update the xpcshell tasks to run from opt. I'll post a new run soon here.
Could we skip Linux 18.04 x64 opt and Windows 11 x64 opt items too?
some of these tasks only ran because of the nature of changes that I had on the push. For example the windows and linux jobs you mentioned ran because of changes in the tryselect itself [1]
That being said, there are some lint/test tasks that "always" run as they are "cheap" enough to run on pretty much every push.
It would probably be nice to avoid some of the builds on Android 5.0 x86-64 opt, Android 5.0 x86-64 debug, Android 5.0 x86-64 debug-isolated-process, and Android 7.0 x86-64 WebRender debug for a time saving opportunity. I'm not sure what is typical though for a general test though and a best practice, what do you recommend?
The Android 5.0
builds seem to be required for some tooling tasks [2]. If we still want those to be avoided, I'd suggest we follow up in a separate issue to make the tooling tasks not depend on those.
[1] https://searchfox.org/mozilla-central/source/taskcluster/ci/source-test/python.yml#365
[2] https://firefox-ci-tc.services.mozilla.com/tasks/J64ITo6eT7G_4wah6y-_9Q
Reporter | ||
Comment 11•11 months ago
|
||
Thanks you so much!
some of these tasks only ran because of the nature of changes that I had on the push.
Ohh, that makes sense, thanks for explaining!
The Android 5.0 builds seem to be required for some tooling tasks [2]. If we still want those to be avoided, I'd suggest we follow up in a separate issue to make the tooling tasks not depend on those.
Sounds good, I don't have a strong preference! Moving away from Android 5.0
long term would probably make sense though.
Assignee | ||
Comment 12•11 months ago
|
||
Updated•11 months ago
|
Comment 13•11 months ago
|
||
Comment 14•11 months ago
|
||
bugherder |
Comment 15•10 months ago
|
||
Hey folks, can we please add these builds in the preset:
- Android 7.0 x86-64 WebRender debug
- Android 7.0 x86-64 Lite WebRender opt
- Android 7.0 x86-64 Lite WebRender Shippable
- Android 7.0 x86-64 Shippable WebRender
Updated•9 months ago
|
Description
•