Closed
Bug 1294256
Opened 8 years ago
Closed 3 years ago
Android host-utils can become outdated (maybe use a toolchain task)
Categories
(Firefox for Android Graveyard :: Testing, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: gbrown, Unassigned)
References
Details
Android tests rely on a host-utils package, downloaded from tooltool, to supply host-side utilities like xpcshell and ssltunnel. The host-utils package is updated manually, generally when someone complains that the existing package is out of date. See bug 1293952, especially: (In reply to Boris Zbarsky [:bz] from bug 1293952 comment #2) > The big problem is that on non-Android server scripts run against nightly. > So it's quite easy to have people write those, tryserver on some non-Android > platform, then check in and break Android tests... Can we implement a new way to access current versions of these utilities without periodic manual intervention? Ideally the solution will apply to both tests in automation and tests run locally via mach.
Reporter | ||
Comment 1•8 years ago
|
||
Let's consider: (In reply to Justin Wood (:Callek) from bug 1293952 comment #3) > * Person (X) Pushes > ** Job (X) uses a special taskcluster kind to generate a host-utils package > -- (TODO: possible to do it as part of the android or desktop build itself?) > ** Test jobs reference this package similarly to how we reference docker > images > ** Taskcluster can possibly optimize out this Job X to not create new > host-utils unless needed. > > That would ensure we let people modify things on try that could affect > host-utils run scripts, as well as lets us use reasonably newer host-utils > on all trees. > > This is probably scoped large enough to be a deliverable for someone though, > and not something I can agree to take on in the forseeable future.
Reporter | ||
Updated•8 years ago
|
Priority: -- → P3
Reporter | ||
Comment 2•7 years ago
|
||
hostutils is in need of an update again. Nick suggested using a toolchain task for periodic hostutils updates.
Reporter | ||
Comment 3•6 years ago
|
||
We've been getting more and more requests for updates. It doesn't take long to build, test and deploy, but more automation would be nice.
Reporter | ||
Comment 4•5 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=1433279#c23 particularly and the associated wip patch.
Reporter | ||
Comment 5•5 years ago
|
||
Comment 6•3 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
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
•