Closed Bug 1094672 Opened 11 years ago Closed 10 years ago

Enable windows and OS X build on gaia-try

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: rickychien, Unassigned)

Details

Some gaia build system related changes need to test on all environments. However, current gaia-try only cover linux. So it will be more efficient if we can enable windows and OS X on gaia-try.
Hi, is that proposal possible? Thanks! :)
Flags: needinfo?(coop)
Flags: needinfo?
Flags: needinfo?
https://treeherder.mozilla.org/#/jobs?repo=gaia-try Looks like you already have some opt tests running on OS X. What other tests are you looking to add? That question applies to Windows as well. In general, OS X and Windows suffer from limited capacity, so we're very cautious about enabling new jobs on those platforms.
Flags: needinfo?(coop)
It will be good if we can enable OS X / Linux / Win build (B) like https://treeherder.mozilla.org/ui/#/jobs?repo=b2g-inbound. What kind of the limited capacity we may suffer from OS X or Windows? And another question is what's the difference between opt and debug tests? (Didn't see any documents for it) Thanks!
Flags: needinfo?(coop)
(In reply to Ricky Chien [:rickychien] from comment #3) > It will be good if we can enable OS X / Linux / Win build (B) like > https://treeherder.mozilla.org/ui/#/jobs?repo=b2g-inbound. I'm still confused here about what you're asking for. The gaia-try treeherder page[1] is already displaying test results against builds generated from mozilla-central[2] on both Linux and Mac. e.g. Linux - http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-linux64_gecko/1415825416/en-US/ Mac - http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-macosx64_gecko/1415825416/en-US/ We already generate Windows builds as well: Windows - http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-win32_gecko/1415825416/en-US/ We also generate debug versions of all those platforms, and more recently we've also started generating Mulet builds as well. Do you need different builds than these? 1. https://treeherder.mozilla.org/ui/#/jobs?repo=gaia-try 2. https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-central > What kind of the limited capacity we may suffer from OS X or Windows? And > another question is what's the difference between opt and debug tests? > (Didn't see any documents for it) Thanks! The opt and debug designation comes from the builds being tested. Opt builds have debug symbols, assertions, etc stripped out for speed and size. Debug builds allow more instrumentation and introspection. The mozconfig files that define the configure params for the builds mentioned above (including for debug) can be found here: https://hg.mozilla.org/mozilla-central/file/default/b2g/config/mozconfigs The capacity issues we face on Windows and Mac stem from the fact that these platforms run on actual physical hardware, versus the AWS instances we can use for Linux. We have finite pools of these machines.
Flags: needinfo?(coop)
Is it that you want to run the b2g_ubuntu64_vm gaia-try opt test gaia-build (Gb on treeherder) b2g_ubuntu64_vm gaia-try opt test gaia-build-unit (Gbu on treeherder) jobs on windows/mac too ?
No, I'm taking about the B on b2g-inbound [1]. Every item in [1] has its B for checking bustage. So I want to enable it on Win/OS X/Linux. [1] https://treeherder.mozilla.org/ui/#/jobs?repo=b2g-inbound&revision=bb35fdd01744
There are several B's there, could you please click on one, then copy the full name from the bottom left corner of the screen. Which part of that build are you interested in ?
I'm interesting in B2G: B2G Desktop Linux opt B2G Desktop Linux x64 opt B2G Desktop OS X opt B2G Desktop Windows opt
From the gaia-try side, the only change that needs to be made here is to add a win32.json file, if we don't rely on the gaia build system to download the gecko to use for the build. Please ni? me again if we need a win32.json file.
Cool! I'm looking forward to seeing the B status in Gaia-try side, and I think Gaia-try should show B on all platforms as I mentioned on comment 8.
Flags: needinfo?(jhford)
(In reply to Ricky Chien [:rickychien] from comment #10) > Cool! > > I'm looking forward to seeing the B status in Gaia-try side, and I think > Gaia-try should show B on all platforms as I mentioned on comment 8. Do we need the win32 file?
Flags: needinfo?(jhford)
I think there's still a disconnect here (at least for me). None of the builds in comment #8 are run on gaia-try at the moment, not even the linux ones. Those compile gecko with ac_add_options --enable-application=b2g and a few more tweaks, and of course gaia. Currently gaia-try consumes those builds (from mozilla-central), but uses gaia from the landing/PR. So let me ask again, which part of that gecko build is what you want ? Perhaps you don't really want that at all.
Even though I don't know anything about win32.json, I'm sure that we don't have to download gecko and even build gecko every time. So I think we should add win32.json file. Thanks!
(In reply to Ricky Chien [:rickychien] from comment #13) > Even though I don't know anything about win32.json, I'm sure that we don't > have to download gecko and even build gecko every time. We only need this file if we need Mozharness to download the gecko used. If the expectation is that the Makefiles themselves will be downloading whichever gecko they need, we do not need this win32.json file. > So I think we should add win32.json file. Thanks! Adding this file should only be done if we can confirm that we actually do need it.
Ok, I misunderstood it. Since we can download b2g from ftp server in gaia, so we don't need the win32.json file. What we want to do is that carry out the command to build gaia and then output the result. However, I'm not familiar with the command which is used by b2g-inbound to build gaia. I don't know who can I ask or maybe you know how to do it?
Flags: needinfo?(jhford)
(In reply to Ricky Chien [:rickychien] from comment #15) > Ok, I misunderstood it. Since we can download b2g from ftp server in gaia, > so we don't need the win32.json file. > > What we want to do is that carry out the command to build gaia and then > output the result. However, I'm not familiar with the command which is used > by b2g-inbound to build gaia. I don't know who can I ask or maybe you know > how to do it? If you can see the log of the test that you're trying to put on gaia-try on b2g-inbound, all of the commands issued will be printed in the logs. As for issuing that command in the actual automation, that's something that Releng will help be able to help you with.
Flags: needinfo?(jhford)
OK! So how to start this? How can I help you?
Ricky - as :coop noted in comment 4 adding these tests will slow down both gaia-try and regular try, so we need to make sure the tradeoff is worth it. Often that is a negotiation between QA, Sheriffs, and development managers. :Howie will check with Ricky to ensure we have understand the goals of this test (in case it is already provided elsewhere). Adding :jgriffin to get insight into whether this is achievable with gaia-try as currently implemented.
Flags: needinfo?(jgriffin)
Flags: needinfo?(hochang)
Thanks Hal. Ricky is out of office today, leaving the ni and I'll check with him face to face tomorrow.
Windows and OSX builds should be ok as long as gaia-try is running in buildbot. As soon as it's moved to TaskCluster, though, which I think should happen soon, Windows and OSX builds won't work. I'd defer to James Lal to decide whether this makes sense now or not.
Flags: needinfo?(jgriffin) → needinfo?(jlal)
In fact, this not in high priority. However, we just wonder if it is feasible and don't have to take too much time and resource. This feature will be pretty convienient to gaia developer who wants to land build-related patch. I thought it is easy to achieve. However, it appears not to be the case. If it could happen in TaskCluster, I'm fine to wait for it.
One of the things I would like to do is stop building gaia on platforms other then linux. It seems (at least for the common gaia cases) our profiles should work just fine cross platform. If the goal is to provide better testing for the build system I think we should use this approach then use profiles generated from linux on windows/osx/etc... this has a side benefit of shaving large amounts of time (though not too much end-to-end time) from all gaia related testing. If the goal is to run tests on OSX/Windows for other reasons we have discussed keeping those platforms alive on current bb infra for some period of time until TC has support for those platforms (windows at least we are targeting next quarter).
Flags: needinfo?(jlal)
Flags: needinfo?(hochang)
Our goal is to provide better testing for the build system, so I agree the advice mentioned on comment 22. Do you agree with it or have another opinion? Thanks!
Flags: needinfo?(hwine)
(In reply to Ricky Chien [:rickychien] from comment #23) > Our goal is to provide better testing for the build system, so I agree the > advice mentioned on comment 22. Do you agree with it or have another > opinion? Thanks! To be explicit, I believe you are agreeing with this part of comment 22: (In reply to James Lal [:lightsofapollo] from comment #22) > One of the things I would like to do is stop building gaia on platforms > other then linux. It seems (at least for the common gaia cases) our profiles > should work just fine cross platform. If the goal is to provide better > testing for the build system I think we should use this approach then use > profiles generated from linux on windows/osx/etc... this has a side benefit > of shaving large amounts of time (though not too much end-to-end time) from > all gaia related testing. As such, there is no action for (firefox) release engineering, and this bug could be resolved as "works for me". Whether or not this approach meets the needs of other groups (such as QA, Sheriffs) is up to those teams.
Flags: needinfo?(hwine) → needinfo?(ricky060709)
I know it's a trade-off between shaving large amounts of time for gaia-try and providing better quality tests in all platforms. I accept that we should save time for each try and keep pushing every build-related patch to try for ensuring builds are green in all platforms.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ricky060709)
Resolution: --- → WORKSFORME
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.