1326140 - [Stylo] Release the linux64-stylo opt build on archive.mozilla.org

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect)

Description

[Shing Lyu [:shinglyu]]

Seems like the linux64-stylo opt build[0] is not available on archive.mozilla.org.

For Stylo's performance testing using Hasal, and for developer to download the tarball for debugging, we need to put the linux64-stylo build on archive.mozilla.org (or somewhere publicly accessible).

[0]: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0b950fb3f9e42bcc990d1f96749ef46e48d1be1b

Comment 1

[Shing Lyu [:shinglyu]]

Sorry if I'm using the wrong component, not sure who to ask.

Comment 2

[Gregory Szorc [:gps]]

This should "just work." Perhaps it isn't because the stylo build tasks are currently failing [so the artifacts aren't being uploaded]?

Comment 3

[Shing Lyu [:shinglyu]]

For example, I can't find this[0] build on archive.mozilla.org[1], or did I look in the wrong place?

[0]: https://treeherder.mozilla.org/#/jobs?repo=try&revision=901f72879bb6b664e8eeeec46f06d677f353fc95
[1]: http://archive.mozilla.org/pub/firefox/try-builds/

Comment 4

[Gregory Szorc [:gps]]

The build task completed successfully. The TC artifacts were uploaded. They just aren't on archive.mo. And I'm not sure why.

What little I know about the archive.mo plumbing is that... there is some magic involved.

mshal: could you please help us figure out why these builds aren't making it to archive.mo?

Comment 5

[Michael Shal [:mshal]]

If you just need any kind of public access, it's probably easiest to grab them through the index. The task inspector for that task ( https://tools.taskcluster.net/task-inspector/#EMAxKHiVSXW0_A206umstA/ ) shows the index routes as:

index.gecko.v2.try.latest.firefox.linux64-stylo-opt
index.gecko.v2.try.pushdate.2016.12.29.20161229091913.firefox.linux64-stylo-opt
index.gecko.v2.try.revision.901f72879bb6b664e8eeeec46f06d677f353fc95.firefox.linux64-stylo-opt

So for example using the revision route you can find the artifacts at: https://tools.taskcluster.net/index/artifacts/#gecko.v2.try.revision.901f72879bb6b664e8eeeec46f06d677f353fc95.firefox.linux64-stylo-opt/gecko.v2.try.revision.901f72879bb6b664e8eeeec46f06d677f353fc95.firefox.linux64-stylo-opt

Or you could grab say the target.tar.bz2 directly with something like wget if you need to automate things:
$ wget https://index.taskcluster.net/v1/task/gecko.v2.try.revision.901f72879bb6b664e8eeeec46f06d677f353fc95.firefox.linux64-stylo-opt/artifacts/public/build/target.tar.bz2

Feel free to ping or ni me if you have trouble using the index.

If you need archive.m.o specifically, you'll probably have to check with nthomas, since I'm not familiar with that side of things unfortunately.

Comment 6

[Shing Lyu [:shinglyu]]

Shako, do you think we can make Hasal grap the firefox tarball from taskcluster?

Comment 7

[Shako Ho]

Hi Shing,

  Sorry for the late response. 

  Will this become a regularly test for stylo? or just one time test?

  If this is a one time test, I will suggest we can do it manually.

Comment 8

[Shing Lyu [:shinglyu]]

We'd want to run it regularly. Is it a lot of work to support downloading the build from taskcluster? If so we can probably delay that until we git it in nightly.

Comment 9

[Shako Ho]

I don't think that will take too much effort on implementing such tool, just need few time to figure out the pattern or rule of build path of task cluster.

But another concern would be the actual bandwidth of our current machine, most of our machines are occupied for regularly run and some debugging request, so we probably cannot add another regular testing for stylo right now. However we are planning to expand our testing machines recently, so what if we provide some quick manual testing for you before our new machines arrived?

Comment 10

[Chris AtLee [:catlee]]

Downloading from the taskcluster index is the correct way forward here.