On Tue, Jun 03, 2014 at 09:11:26AM -0700, Gregory Szorc wrote: > On 6/3/14, 6:42 AM, Ben Hearsum wrote: > >On 14-06-03 06:39 AM, Gabor Krizsanits wrote: > >>>From time to time, no matter what platform I use, the build configuration > >>>on the try server changes > >>and from that point on it's just a matter of time that my build gets > >>broken. When you're > >>about to work on some urgent fixes, it can be very frustrating to try and > >>fix the build instead... > >> > >>I think we only support the exact configurations that we are testing > >>against on the try server. Anything > >>else (that is untested) will be broken. We should fix those... but it will > >>happen from time to time. > >>So one thing we can do is to communicate it clearly what is the exact env. > >>on the try server, (os version, > >>gcc version, on windows SDK version, etc.) and warn people when it's > >>changed. Or we have to do > >>automated tests for more envs (which is resource wise won't be > >>easy/feasible) > >> > >>I really cannot blame people for breaking the build on env we are not > >>testing against on the try server, > >>(especially not with warnings-as-errors turned on...) for obvious reasons. > >>But I think we could > >>do better about announcing any changes on it early, so we could all update > >>or systems in time > >>accordingly, and avoid having to deal with these kind of problems in the > >>worst possible time. > >> > >> - Gabor Krizsanits > >> > > > >It's pretty rare that things such OS, Compiler, SDK change on our build > >systems. We do tend to make noise about them when that happens, too. Do > >you have specific examples to point at? > > > >In any case, it's good to keep in mind that Try follows mozilla-central > >in terms of build configuration and requirements -- which means it's > >inherently unstable. We make no guarantees about build requirements > >staying static for any period of time. > > Perhaps this would be a good opportunity for someone to chime in about the > Docker-ization efforts currently underway. Will those efforts lead to e.g. a > docker image ID embedded in the tree so that an automation job will use an > appropriate environment depending on the code pushed (as opposed to what's > deployed on the server at the time of the push)?
The system compiler in the mock environment is gcc 4.4 or 4.3, I don't remember. We haven't used it in a *very* long time. Then, there are mozilla packages for 4.5 and 4.7 that are installed, and we're not using them either. We're using tooltool to download a compiler that is defined in-tree[1]. So we're already there, albeit not using docker[2] Mike 1. See e.g. files under browser/config/tooltool-manifests. 2. Note that a docker id doesn't guarantee that the image doesn't change either. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
