Cannot find GeckoView-example nightlies in taskcluster index
Categories
(Firefox Build System :: Task Configuration, defect)
Tracking
(Not tracked)
People
(Reporter: mstange, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Up until May 20th, this URL pointed to the latest GeckoView-example Nightly build:
https://firefox-ci-tc.services.mozilla.com/api/index/v1/task/gecko.v2.mozilla-central.nightly.latest.mobile.android-api-16-opt/artifacts/public/build/geckoview_example.apk
However, that path seems to have stopped updating. Indeed, this directory only lists months until May:
https://firefox-ci-tc.services.mozilla.com/tasks/index/gecko.v2.mozilla-central.nightly.2020
Where are GeckoView-example nightlies located now?
Reporter | ||
Comment 1•4 years ago
|
||
Oh, maybe I need to look for PGO builds rather than "nightly" builds now? For example:
https://firefox-ci-tc.services.mozilla.com/api/index/v1/task/gecko.v2.mozilla-central.latest.mobile.android-api-16-pgo/artifacts/public/build/geckoview_example.apk
Do we upload symbols for all PGO builds?
Comment 2•4 years ago
|
||
so I think you want gecko.v2.mozilla-central.shippable.latest.mobile.android-api-16-opt e.g. https://github.com/mozilla-mobile/fenix/pull/10661
If there is a place you're using this stuff (indexes) that I missed, I would be interested in where.
I'm also more than happy to discuss more details on "what" this change was, etc.
[I suggest a RESO/??? status on this bug]
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
Thanks! Then I still have the other question - do we upload symbols for all the shippable builds?
My main use case for recent GVE builds is profiling, and narrowing down whether something is a bug in Fenix or in Gecko. For example, when somebody reports a bug or a performance problem in Fenix, often the next step is to check whether it also happens in GeckoView-example. So we'll want to use a GVE build that uses a similarly-recent Gecko to the Fenix Nightly build that the problem was reported on.
And for profiling, we need to have symbols for the GVE build on the mozilla symbol server.
I currently point to the old taskcluster path from the documentation at https://profiler.firefox.com/docs/#/./guide-remote-profiling . Actually, looking at that document, I also point to the following Fenix path:
https://firefox-ci-tc.services.mozilla.com/tasks/index/project.mobile.fenix.v2.nightly/latest
... which is 17 days old. Is there a "shippable" variant for Fenix as well?
By the way, I tried to look for something like gecko.v2.mozilla-central.shippable.latest from the taskcluster index, but wasn't successful. I might have been more successful if there was some indication on https://firefox-ci-tc.services.mozilla.com/tasks/index/gecko.v2.mozilla-central.shippable that a "latest" subpath exists. It is probably listed on the last page, but the pagination interface isn't very useful in getting me there...
Comment 4•4 years ago
|
||
(In reply to Markus Stange [:mstange] from comment #3)
Thanks! Then I still have the other question - do we upload symbols for all the shippable builds?
Pretty much, yes. The intent is that these do everything that a Nightly needs... (there are some cases where we don't on different trees, but afaict we do always on central)
I currently point to the old taskcluster path from the documentation at https://profiler.firefox.com/docs/#/./guide-remote-profiling . Actually, looking at that document, I also point to the following Fenix path:
https://firefox-ci-tc.services.mozilla.com/tasks/index/project.mobile.fenix.v2.nightly/latest
... which is 17 days old. Is there a "shippable" variant for Fenix as well?
This recently changed [1] in index path for Fenix, you'll now want:
https://firefox-ci-tc.services.mozilla.com/api/index/v1/task/mobile.v2.fenix.nightly.latest.armeabi-v7a/artifacts/public/build/armeabi-v7a/target.apk
(and similarly: https://firefox-ci-tc.services.mozilla.com/api/index/v1/task/mobile.v2.fenix.nightly.latest.arm64-v8a/artifacts/public/build/arm64-v8a/target.apk )
I just created a PR for this change from that documentation as well https://github.com/firefox-devtools/profiler/pull/2700
By the way, I tried to look for something like gecko.v2.mozilla-central.shippable.latest from the taskcluster index, but wasn't successful. I might have been more successful if there was some indication on https://firefox-ci-tc.services.mozilla.com/tasks/index/gecko.v2.mozilla-central.shippable that a "latest" subpath exists. It is probably listed on the last page, but the pagination interface isn't very useful in getting me there...
Unfortunately the index route browser is not really intended for humans to browse it as well, its more for programatic access and some rudimentary human access. I am however hopeful that I can find some cycles to try and prioritize a combination of some restructuring (likely with a gecko.v3
) and some in-tree tests for 3rd party consumers, with those tests being the only guaranteed way we support out-of-tree users, either by notification when stuff is going away, or something. - That sort of change is not on my current plate though.
Updated•3 years ago
|
Comment 5•11 months ago
|
||
I think comment 4 answered this (though mobile index paths have changed again since then); feel free to reopen if there's missing indices still.
Description
•