Closed Bug 1364095 Opened 8 years ago Closed 8 years ago

add AWSY to OSX for trunk/try and let it ride the trains.

Categories

(Release Engineering :: General, enhancement)

enhancement
Not set
normal

Tracking

(firefox56 fixed)

RESOLVED FIXED
Tracking Status
firefox56 --- fixed

People

(Reporter: jimm, Assigned: bc)

References

(Depends on 1 open bug)

Details

(Whiteboard: [e10s-multi:?])

Attachments

(1 file)

The e10s team is currently using beta repo try pushes plus manually selected runs of the AWSY test to acquire memory measurements for e10s multi release criteria. Currently this works for Linux and Windows, but OSX+AWSY TC runs don't show up with the "Add new jobs" treeherder interface. This bug is about getting OSX added as a hardware target for TC AWSY runs.
we need to determine if this runs on osx; then if so, adding this to buildbot as an option for osx on try would be the next step; In addition this would need taskcluster modifications as all osx is scheduled via taskcluster now but run on buildbot.
osx now runs on TC only- I propose we run AWSY on OSX as we do for linux/windows per comment, and of course e10s only to save electronic trees.
Flags: needinfo?(bob)
Assignee: nobody → bob
Summary: Allow manual execution of AWSY + OSX on try → add AWSY to OSX for trunk/try and let it ride the trains.
Attached patch awsy-osx.patchSplinter Review
This keeps the same-run-on-projects as linux and windows which is release, trunk, try. See http://searchfox.org/mozilla-central/source/taskcluster/docs/attributes.rst#run_on_projects for the definitions. try runs: https://treeherder.mozilla.org/#/jobs?repo=try&author=bclary@mozilla.com&fromchange=9473270debb319548cdaff538fc19a4560307493&tochange=466a0f743ec4eabc36b1fe8560df2282eee997f3 The first run had an error in the minidump_stackwalk path, but otherwise ran ok.
Flags: needinfo?(bob)
Attachment #8881128 - Flags: review?(jmaher)
Attachment #8881128 - Flags: review?(erahm)
Comment on attachment 8881128 [details] [diff] [review] awsy-osx.patch Review of attachment 8881128 [details] [diff] [review]: ----------------------------------------------------------------- ::: taskcluster/ci/test/test-platforms.yml @@ +206,5 @@ > macosx64-nightly/opt: > build-platform: macosx64-nightly/opt > test-sets: > - macosx64-tests > + - awsy will nightly and opt be tracked on the same graph? Ideally not, but I am not sure what build differences there are between them
Attachment #8881128 - Flags: review?(jmaher) → review+
I don't know but I bet they are. I don't see any distinction in the perfherder ui. Should I just remove that ?
I would remove nightly- this should run ok on central, try, trunk; not sure if it will go to beta with opt- I guess we can figure that out.
Done in my local version of the patch. It is not clear to me how pgo is handled in beta. Only linux64-pgo/opt is defined in beta anyway.
osx we do not have pgo; oddly, for talos we don't seem to run linux64-pgo, only linux64-nightly on beta- so I am confused as to what we build on beta as well.
Comment on attachment 8881128 [details] [diff] [review] awsy-osx.patch Review of attachment 8881128 [details] [diff] [review]: ----------------------------------------------------------------- Thanks! Excited to see this on OSX :)
Attachment #8881128 - Flags: review?(erahm) → review+
Pushed by bclary@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/8f2c971c9630 add AWSY to OSX for release/trunk/try, r=erahm,jmaher.
Depends on: 1377998
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: