Re: Soft code freeze for Firefox 88 starts March 18

Hello again. The Nightly version number has been bumped to 89 and the soft freeze is now over. Thanks, Ryan On Mon, Mar 15, 2021 at 12:43 PM Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > Hi all, > > With Firefox 87 RC shipping soon, we are nearing the end of the Nig

Soft code freeze for Firefox 88 starts March 18

Hi all, With Firefox 87 RC shipping soon, we are nearing the end of the Nightly 88 cycle. In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 88 to a wider audience with confidence next week, we'd like to ask that any risky changes be

Sunsetting “Check-in Needed”

Hello, For a long time now, we have relied on some form of a “Check-in Needed” flag in Bugzilla or Phabricator to assist in getting patches landed when the patch authors were unable to do so themselves. This has served us well for a long time, especially in the days when pushing patches was a

PSA: Avoid the MSVC 2019 16.7.0 Update

FYI, Microsoft released a major MSVC 2019 update recently - version 16.7.0. At the moment, Firefox does *not* build with that release. To avoid disruptions in local development flow, stick to version 16.6 for the time being. Bug 1657913 is filed for the bustage. Thanks, Ryan

Re: New system for landing + cancelling landing jobs in Lando

Being able to cancel landing requests has been a top request for a long time and will allow us to save computing resources on unwanted pushes. Thanks for making this possible! -Ryan On Thu, Jul 16, 2020 at 12:30 PM Zeid Zabaneh wrote: > Greetings everyone, > > The new Lando landing worker

Re: Soft code freeze for Firefox 79 starts June 25

Hello, the Nightly version bump to 80 was completed successfully today and the soft freeze is now lifted. Thanks, Ryan On Wed, Jun 24, 2020 at 11:18 AM Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > With Firefox 78 now in the RC phase, we are nearing the end of the Nightly >

Soft code freeze for Firefox 79 starts June 25

With Firefox 78 now in the RC phase, we are nearing the end of the Nightly 79 cycle. In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 79 to a wider audience with confidence next week, we'd like to ask that any risky changes be avoided

Re: Soft code freeze for Firefox 76 starts April 2

Hello, The Nightly version number increase has landed on mozilla-central and the soft freeze is now complete. Thanks, Ryan On Tue, Mar 31, 2020 at 11:20 PM Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > Hi all, > > With Firefox 75 RC shipping soon, we are

Soft code freeze for Firefox 76 starts April 2

Hi all, With Firefox 75 RC shipping soon, we are nearing the end of the Nightly 76 cycle. In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 76 to a wider audience with confidence, we'd like to ask that any risky changes be avoided from

Re: Soft code freeze for Firefox 73 starts January 2

Hi all, The Nightly version has been bumped to 74 and with that, the soft freeze has ended. Thanks, Ryan On Tue, Dec 31, 2019 at 1:42 PM Liz Henry (:lizzard) wrote: > Hello everyone, > > We're nearing the end of the Nightly 73 cycle as well as the end of the > year and the decade! > > In

Re: Soft Code Freeze for Firefox 69 starts July 1st

The Gecko version on mozilla-central has now been bumped to 70 and with that, the soft freeze is over. Thanks, Ryan On Tue, Jun 25, 2019 at 1:37 PM Pascal Chevrel wrote: > Hi all, > > On July 1st, we will be merging Firefox 69 from mozilla-central to beta > for the first time. In order to

Re: Fennec moving to extended support

That is correct. On Fri, Apr 26, 2019, 06:26 Mike Hommey wrote: > On Thu, Apr 25, 2019 at 09:10:36PM -0400, Ryan VanderMeulen wrote: > > Hello everyone, > > > > tl;dr: Fennec will be following the 68 train to ESR68-based release. > > > > Why are we doing it?

Fennec moving to extended support

Hello everyone, tl;dr: Fennec will be following the 68 train to ESR68-based release. Why are we doing it? We want to provide users with a secure and supported legacy Firefox for Android until Fenix has matured enough for users to migrate to it. Therefore, starting from Gecko 68, we plan to use

Post-Holiday reviews and needinfo responses

Hi everyone, happy New Year! As you return to work, please be sure to look through your open review (in Bugzilla and Phabricator) and needinfo requests at your earliest convenience. We've got about 2 weeks remaining in the Fx65 Beta cycle before we start creating RC builds, so time is short for

Re: Soft code freeze for Firefox 65 starts December 3

The Gecko version has been bumped to 66 now on mozilla-central, so the soft freeze is now over. Thanks, Ryan On Thu, Nov 29, 2018 at 10:13 AM Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > Hi all, > > On December 3, we will be merging Firefox 65 from mozilla-

Soft code freeze for Firefox 65 starts December 3

Hi all, On December 3, we will be merging Firefox 65 from mozilla-central to beta for the first time. In order to avoid invalidating the testing we get out of late Nightly and the early Developer Edition builds and to ensure that we can roll out Beta 65 to a wider audience with confidence, we'd

Re: Moving Windows MSVC Builds Back To Tier 1

As was noted in the bug, deciding to explicitly un-support MSVC is a decision which merits wider discussion and is not something I wanted to tackle in that bug. -Ryan On 10/12/2018 4:08 PM, Dave Townsend wrote: If we've made the decision to stick with clang-cl, why would we continue to

Moving Windows MSVC Builds Back To Tier 1

When we made the decision to switch to clang-cl for our Windows builds, MSVC builds and tests were kept running as Tier 2 jobs in CI to ensure that they continued working in the event of an emergency switch-back caused by any last-minute clang-cl compatibility issues. Thankfully, no such issues

Re: Soft code freeze for Firefox 63 starts August 23

Hello everyone, August 23rd is now upon us and the soft freeze has begun. It will end on September 4 once the Gecko version number is bumped to 64 on mozilla-central. Thanks, Ryan On Thu, Aug 16, 2018 at 11:14 AM Pascal Chevrel wrote: > Hello, > > This is a reminder that the Nightly Soft

PSA: Avoid Visual Studio 2017 15.7.0

Yesterday, Microsoft released Visual Studio 2017 15.7.0. Unfortunately, it is currently not usable for building Firefox due to bug 1458247 (internal compiler errors in WebRTC code). The bug was already reported and confirmed upstream during the 15.7 preview cycle, but unfortunately the final

Re: Soft code freeze for Firefox 61 starts April 26

t; > On Fri, Apr 20, 2018 at 5:43 PM, Ryan VanderMeulen < > rvandermeu...@mozilla.com> wrote: > >> Just a reminder that this is now less than a week away. Please be mindful >> of any large/risky patches targeting 61 as time is running low to land them >> before the

Announcing MozillaBuild 3.2 Release

MozillaBuild 3.2 is a minor update to version 3.1.1 mostly focusing on updating a few of the bundled components to newer versions. https://ftp.mozilla.org/pub/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Important changes since version 3.1.1: * Updated Python2 to version 2.7.15 and

Re: Soft code freeze for Firefox 61 starts April 26

As a follow-up, the soft freeze is officially in effect until the version bump to 62 takes place on Monday, May 7th. Please use discretion when pushing changes to mozilla-central between now and then. Thanks, Ryan On Fri, Apr 20, 2018 at 5:43 PM, Ryan VanderMeulen < rvandermeu...@mozilla.

Re: Soft code freeze for Firefox 61 starts April 26

Just a reminder that this is now less than a week away. Please be mindful of any large/risky patches targeting 61 as time is running low to land them before the soft freeze begins. Thanks, Ryan On Thu, Apr 12, 2018 at 10:56 AM, Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: &g

Soft code freeze for Firefox 61 starts April 26

Hi all, On April 26th, we will be merging Firefox 61 from mozilla-central to beta for the first time. In order to avoid invalidating the testing we get out of late nightly and the early Developer Edition builds and to ensure that we can roll out Beta 61 to a wider audience with confidence, we'd

PSA: Visual Studio 2017 15.6 now required to build 61+

While I know I'm tempting fate by sending this out while the patches are still on autoland, I wanted to start giving people a heads-up now that bug 1424281 has been pushed, which will make Visual Studio 2017 15.6 (Update 6) the minimum version required to build Gecko 61+ once it merges to m-c.

Re: PSA: Build bustage with Visual Studio 2017 15.6

As an update, the fix for bug 1443367 has been merged to m-c. There doesn't appear to be any other bustage lurking behind it, so updating should be less fraught with peril now. -Ryan On Mon, Mar 5, 2018 at 7:41 PM, Ryan VanderMeulen <rvandermeu...@mozilla.com > wrote: > Today,

PSA: Build bustage with Visual Studio 2017 15.6

Today, Microsoft released version 15.6 of Visual Studio 2017: https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes After updating and attempting to build with it locally, I encountered build bustage that I've filed as bug 1443367. I don't know if there will be further issues

Re: MinGW Target on TaskCluster

On 2/6/2018 6:36 PM, Aaron Klotz wrote: Furthermore, can we clarify whether mingw is currently a tier 1 or tier 2 platform? Earlier in this thread, mingw was denoted as tier 2 (and it still shows up as tier 2 on treeherder), yet sheriffs are backing out patches when mingw bustage occurs. Tor is

Re: Firefox build issues with Rust and the new VS2017 15.5 update

The fix for bug 1423649 has been merged to m-c. You *should* be good to go now :-) -Ryan On Thu, Dec 7, 2017 at 11:46 PM, Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > That's the issue Adam raised, separate from the clang one. It's tracked in > bug 1423649. For now,

Re: Firefox build issues with Rust and the new VS2017 15.5 update

90.0 % > 0:35.46 Downloading... 95.0 % > 0:36.11 Downloading... 100.0 % > 0:36.12 Downloaded artifact to c:\Users\jameswc\.mozbuild\ > toolchains\1e9883794cf0be12-clang.tar.bz2 > 0:36.47 untarring "c:\Users\jameswc\.mozbuild\clang.tar.bz2" > > Your system should be

Re: Firefox build issues with Rust and the new VS2017 15.5 update

Bug 1423307 has been merged to m-c now. After you've updated m-c, you can re-run |./mach bootstrap| to pick up the newer clang binaries that will fix the _Ty problem. -Ryan On Tue, Dec 5, 2017 at 2:14 PM, Ryan VanderMeulen <rvandermeu...@mozilla.com > wrote: > As a follow-up, it l

Re: Firefox build issues with Rust and the new VS2017 15.5 update

below until the in-tree changes are landed: https://queue.taskcluster.net/v1/task/Q7sN0gfPSE-OAEV5vuGtEA/runs/0/artifacts/public/build/clang.tar.bz2 -Ryan On Tue, Dec 5, 2017 at 11:16 AM, Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > FYI, the VC++ 2017 v14.12 toolset

Firefox build issues with Rust and the new VS2017 15.5 update

FYI, the VC++ 2017 v14.12 toolset included in the recently-released VS2017 15.5 update appears to have broken building Firefox due to issues with the Rust compiler (in particular, the version of libclang we ship with it) and one of the system headers:

Announcing MozillaBuild 3.1.1 Release

Well, that didn't go as planned. Due to a couple regressions from version 3.1, version 3.1.1 has been released to clean up the regressions. Apologies for the delay in getting this out as I know the hg issue in particular has been painful for people hitting it. The two primary changes are: * Fix

Announcing MozillaBuild 3.1 Release

MozillaBuild 3.1 is a minor update to version 3.0 mostly focusing on updating a few of the bundled components to newer versions. I would advise updating to it at your earliest convenience. https://ftp.mozilla.org/pub/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Important changes since

Re: Visual Studio 2017 coming soon

On 10/26/2017 10:14 AM, Milan Sreckovic wrote: Are we locked into using the same compiler for the ESR updates?  In other words, do we need to keep VS2015 for ESR52 builds until they are not needed anymore? Our compiler toolchains are determined with in-tree configs nowadays, so this change

Re: We need better canaries for JS code

Note that we also have bug 920191 on file for making JS exceptions fatal in the harness. One of the big blockers to that has always been cleaning up the existing set of problems, but maybe it would be helpful for some of these issues if/when we could drive that into happening. -Ryan On Wed, Oct

Re: [Sheriffs] Intent to Implement: Remove Treeherder Exclusion Profiles in lieu of Tiers

How will this work with release branches like ESR52? On Wed, Sep 13, 2017 at 1:25 PM, Cameron Dawson wrote: > Just an update that Bug 1387640 is progressing and soon the “Excluded > Jobs” button in Treeherder will disappear. > > We have rolled out the changes to our staging

Re: 57 beta cycle: 57beta/devedition published earlier + soft freeze

In general, I would say your best bet is to have patches landed by mid-day PDT the day before if you want to be reasonably confident that it'll get merged over to Beta in time. Predicting when merges will happen is difficult due circumstances like build/test failures, infra issues, etc. It's

Re: Quantum Flow Engineering Newsletter #20

Is there a good way to get a sense of what the higher-impact bugs are that remain for improving Speedometer? Just going through the deps is difficult because it's hard to assess how much of a win some of those are. Are we gated mostly on JS perf at this point? Layout? Something else? :-) Thanks!

Re: 64-bit Firefox progress report: 2017-07-18

On 8/7/2017 3:51 AM, Chris Peterson wrote: Do we test 32-bit Firefox on Win32 or Win64 today? Our Win32 tests run on 32-bit Windows 7 instances. I don't know offhand if we're using the /3GB switch or not. -Ryan ___ dev-platform mailing list

Re: Announcing MozillaBuild 3.0 Release

; > > On 22 Jul 2017, at 06:02, Ryan VanderMeulen <rvandermeu...@mozilla.com> > wrote: > > > > I am pleased to announce the final release of MozillaBuild 3.0! Sorry in > > advance for the length of this message, but there's a lot of changes in > > this rele

Re: Announcing MozillaBuild 3.0 Release

It appears that the formatting of that email was pretty well destroyed when sent out. Here's a direct link to the release notes in Google Doc form: https://docs.google.com/document/d/1NDz7ROxTYNB5YnP7VJ5CmJomQDun-7o4HDtSRLkuPaw/edit -Ryan On Fri, Jul 21, 2017 at 6:02 PM, Ryan VanderMeulen

Re: Announcing MozillaBuild 3.0 Release

Apologies as well for the awful formatting job there. Thanks Gmail. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Announcing MozillaBuild 3.0 Release

I am pleased to announce the final release of MozillaBuild 3.0! Sorry in advance for the length of this message, but there's a lot of changes in this release worth calling out. https://ftp.mozilla.org/pub/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe

Re: upcoming requirements changes for Stylo builds + request for help

On 5/27/17 8:33 AM, Nathan Froyd wrote: 3. Follow the instructions printed out about applying changes to your mozconfig. You may want to use a separate mozconfig than what you normally use. Are there plans to do something akin to profile-rustup.sh for Windows eventually?

Re: Have you run 'mach bootstrap' lately?

On 5/12/17 6:16 PM, Gregory Szorc wrote: Isn't that something that mach bootstrap should be doing? Yes. A patch is in Ryan's review queue to do this. Said patch is now merged to mozilla-central! :-) -Ryan ___ dev-platform mailing list

Re: Have you run 'mach bootstrap' lately?

On 5/11/17 11:08 PM, Geoffrey Brown wrote: If you set up your build environment with 'mach bootstrap' but haven't run it recently, consider taking a few minutes now to run it again. Running 'mach bootstrap' from time to time will keep your environment up to date and (more-or-less) in sync with

Re: Changes to Firefox repositories on hg.mozilla.org

On 4/6/2017 7:13 PM, Gregory Szorc wrote: https://mozilla-version-control-tools.readthedocs.io/ en/latest/hgmozilla/installing.html Just to call it out explicitly since I've seen the question come up a number of times recently - Windows Mozillabuild users do *not* need to wait for a

Re: Async Iteration is available on non-release-only, for testing purpose

Let's make sure to add a test that's expected to fail as well for this so we can verify that we don't accidentally ship this enabled in chrome. Not that we've had any recent instances of thinking we'd disabled a feature only for it to get unknowingly shipped :) -Ryan On 3/27/2017 12:31 PM,

Nightly updates frozen

Due to some font-related topcrashes, nightly build updates are currently frozen on yesterday's build. Backouts that'll hopefully fix it are on mozilla-central and respins are in progress. Once they're finished, RelEng will un-freeze. Thanks, Ryan ___

Late-cycle Regression Bug Analysis

I was recently asked to look at regression bugs found late in the beta cycle or post-release to see what discernible trends there might be and how it might inform our testing strategy going forward. I looked at all bugs that met those criteria that were filed against Firefox 46-50 up through

Please don't abuse "No bug" in commit messages

A friendly reminder that per the MDN commit rules, the use of "No bug" in the commit message is to be used sparingly - in general for minor things like whitespace changes/comment fixes/etc where traceability isn't as important.

Re: Aarch64 as higher than tier-3?

On 1/23/2017 1:00 PM, Henri Sivonen wrote: Are there any plans to support Aarch64 as a tier higher than tier-3? For Android or the upcoming Aarch64 flavor of Windows 10 maybe? Is Google shipping a 64-bit Android emulator for aarch64 yet? Last I knew, they only supported x86 for their 64-bit

Re: What are your use cases for the Touch Bar on the new MacBook Pro?

Will this API be accessible to addons? Seems like this would be a good place for people to explore and iterate. On 1/3/2017 12:17 PM, Stephen A Pohl wrote: We will develop[1] a solid 1.0 API around the top features to get the ball rolling and will iterate on these going forward.

Re: tier-2 Windows clang-cl static analysis builds running on inbound

On 12/23/2016 3:21 PM, Nicholas Nethercote wrote: Hooray! What is the name of the job on Treeherder? I see a "Windows 2012 x64 opt Executed by TaskCluster build-win64-clang/opt tc(Bcl)" job (and some minor variations) but I suspect that's not the new static analysis one? There's a tc(S) job

Re: Expanding regular regression triage to include crashes?

I like the idea in principle, but in practice, two meetings a week is already not enough to get through regression bugs. Are we going to add more meetings to accommodate this? And I'll note that already, attendance of the regular regression triage meetings has declined from where it was a

Re: Firefox Engineering TMO Survey

Just a friendly reminder to please consider filling out this survey if you haven't already done so. We've already gotten a lot of great feedback and we'd love to get more! It will be open for responses until Friday the 30th. Thanks! -Ryan On 9/23/2016 3:25 PM, Ryan VanderMeulen wrote

Re: Firefox Engineering TMO Survey

Looks like the body of the email got lost! In order to make telemetry.mozilla.org (TMO) and related sites a tool that better supports the needs of the Firefox engineering teams, we would like to collect feedback about people's experiences using these tools. It shouldn't take more than a few

Re: Checkin-needed requests - Please include complete information in the commit message :)

FWIW, there's also an MDN page that documents a lot of this as well: https://developer.mozilla.org/en-US/docs/Mercurial/Using_Mercurial#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F -Ryan On 7/8/2016 2:32 AM, Carsten Book wrote: Hi, someone might not know that doing

Re: Updating 32-bit Windows users to 64-bit Windows builds?

Flash installs the 32-bit and 64-bit plugin versions side by side already (in System32 and SysWOW64, respectively), so I don't think that's an issue here. -Ryan On 5/12/2016 3:38 PM, Lawrence Mandel wrote: Do we need this criteria? RAM - Does it hurt to move an instance that has <4GB? NPAPI

Re: Two talos jobs for PGO builds on fx-team and m-i

On 5/12/2016 10:51 AM, Armen Zambrano G. wrote: IIUC, we have PGO builds running on fx-team and m-i every 6 hours. This only affects Linux x64 and Windows (not Mac). The test pools are shared between all repositories. This entails 14 extra jobs for Windows XP and Windows 8. This entails 16

Re: Ignoring viewpoints of non-Mozilla-employees can't be the way to go for a OSS project!

On 5/9/2016 2:23 PM, Tobias B. Besemer wrote: Hi! Ignoring viewpoints of non-Mozilla-employees can't be the way to go for a OSS Project! The same mistake made Oracle with OpenOffice! Now the project is almost death! Think Mozilla should find his way back to his roots! Would be nice, if some

PSA: Cancel your old Try pushes

I'm sure most of you have experienced the pain of long backlogs on Try (Windows in particular). While we'd all love to have larger pools of test machines (and our Ops people are actively working on improving that!), one often-overlooked thing people can do to help with the backlog Right Now is to

Re: Announcing MozillaBuild 2.2.0 Release

Darn it, I caught and fixed that when I posted the link in the tracking bug for 2.2.0 but missed it in this post. Anyway, the installer is signed by MoCo for this release, so you can verify that what you downloaded is legit that way. Also, you can verify that the sha256 hash is

Announcing MozillaBuild 2.2.0 Release

I am pleased to announce the final release of MozillaBuild 2.2.0. http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Important changes since version 2.1.0: * Updated Mercurial to version 3.7.3. * Added the optional hgwatchman extension (disabled by

Re: Intent to deprecate: MacOS 10.6-10.8 support

On 3/10/2016 6:38 PM, Nils Ohlmeier wrote: Excuse my ignorance, but what means “deprecate support” exactly? I’m only asking because of the opposing reply’s so far. I’m assuming it means we stop testing and building/releasing for these. Would it be a possible alternative to turn of the tests,

Re: Intent to deprecate: MacOS 10.6-10.8 support

On 3/10/2016 5:47 PM, Masatoshi Kimura wrote: Some fullscreen tests are enabled only on 10.6: https://dxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/chrome/chrome.ini#40 This proposal will virtually disable the fullscreen tests on OS X. |skip-if = os != 'mac' || os_version ==

Re: Intent to deprecate: MacOS 10.6-10.8 support

25% is pretty close for 10.6-10.8 combined. However, the current proposal includes security patches for nearly a year still (putting them on the ESR45 train), so construing this as abandoning those users seems like it's going a bit far. On Thu, Mar 10, 2016 at 5:25 PM, Mike Hommey

Re: To bump mochitest's timeout from 45 seconds to 90 seconds

I'd have a much easier time accepting that argument if my experience didn't tell me that nearly every single "Test took longer than expected" or "Test timed out" intermittent ends with a RequestLongerTimeout as the fix. -Ryan On 2/9/2016 12:50 PM, Haik Aftandilian wrote: On Tue, Feb 9, 2016

Re: mozregression – Engineering Productivity Project of the Month

I also just want to give Julien a shout out for the fantastic work he's been doing to make the tool both more versatile and also more user-friendly. If you haven't used it in awhile, give it a look! -Ryan On Mon, Jan 11, 2016 at 2:46 PM, Benoit Girard wrote: > I wanted to

Re: Using the Taskcluster index to find builds

On Mon, Nov 30, 2015 at 7:00 PM, Ryan VanderMeulen <rya...@gmail.com> wrote: On 11/30/2015 3:43 PM, Chris AtLee wrote: The RelEng, Cloud Services and Taskcluster teams have been doing a lot of work behind the scenes over the past few months to migrate the backend storage for builds from t

Re: Using the Taskcluster index to find builds

On 11/30/2015 3:43 PM, Chris AtLee wrote: The RelEng, Cloud Services and Taskcluster teams have been doing a lot of work behind the scenes over the past few months to migrate the backend storage for builds from the old "FTP" host to S3. While we've tried to make this as seamless as possible, the

Announcing MozillaBuild 2.1.0 Release

I am pleased to announce the final release of MozillaBuild 2.1.0. All users are encouraged to upgrade as soon as possible due to many improvements in Mercurial since the last release. http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Important changes

Re: Sheriffing Newsletter, End of September Edition

Included auto-closed bugs in that count sounds misleading at best. On Mon, Sep 28, 2015 at 1:52 PM, Wes Kocher wrote: > What if the query was changed to only count bugs resolved 'fixed'? I > believe all of the inactive intermittent bugs get closed as worksforme or >

Re: |hg bzexport| and Bugzilla two-factor authentication

On 9/16/2015 2:32 PM, Gijs Kruitbosch wrote: Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1205376 . FWIW, part of the reason I've been using tortoisehg is that it used to make bzexport work, when it didn't work on Windows with the hg that shipped with mozillabuild. It's a little ironic

Re: Shutdown hangs are very common

On 7/6/2015 4:34 PM, Vladan D wrote: Background: Firefox shutdown hangs are turned into shutdown crashes by a watchdog thread [1] that forces a crash if shutdown hasn't completed within 1 minute. Thanks to the watchdog and the Windows profile unlocker [2], shutdown hangs aren't as frustrating

Revisions to the Job Visibility Policy

For a little over 2 years, our Job Visibility Policy has been in place to identify all the requirements necessary for a build or test suite to be visible in our infrastructure. https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy However, little has changed with the policy since TBPL was

Re: web-platform-tests on debug builds running on try

On 6/30/2015 7:35 PM, James Graham wrote: Web-platform-tests are now running in debug builds on try only. However due to some teething problems, they are not currently all green. This is expected to be fixed in the next 24 hours but, in the meantime, if you see some orange that seems unrelated

Re: Announcing MozillaBuild 2.0.0 Release

For those who are interested, bug 1119082 tracks adding build support for MSVC 2015. On Sun, Jun 14, 2015 at 9:00 PM, Xidorn Quan quanxunz...@gmail.com wrote: On Sun, Jun 14, 2015 at 9:03 AM, Ryan VanderMeulen rvandermeu...@mozilla.com wrote: SIGNIFICANT CHANGES * Added support

Announcing MozillaBuild 2.0.0 Release

After a long wait, I am pleased to announce the final release of MozillaBuild 2.0.0. http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Much has changed since version 1.11.0, hence the change in major version number. It is STRONGLY advised that this not be

Re: The War on Warnings

I'm 99% sure we've had mis-stars on intermittent assertion oranges where the assertion changed and nobody bothered checking the logs to notice. Various media tests are coming to mind for when that's happened. On 6/10/2015 10:10 AM, Ehsan Akhgari wrote: On 2015-06-10 3:38 AM, David

Re: The War on Warnings

On 6/9/2015 8:33 AM, Robert O'Callahan wrote: Does anyone know of a case where we had a regression that traded one assertion for another? I don't. Rob How would we have found out? :) ___ dev-platform mailing list dev-platform@lists.mozilla.org

Re: DXR 2.0 staged. Feedback please!

On 6/3/2015 3:10 PM, Erik Rose wrote: DXR 2.0 is about to land! This is a major revision touching every part of the system, swapping out SQLite for elasticsearch, and replacing many hard-coded C++ assumptions with a language-independent plugin interface. Please take it for a spin on the

Re: Excessive inbound bustage

On 4/21/2015 4:56 PM, jmath...@mozilla.com wrote: I think we're being bit too sensitive here, I'm sure we can all handle a little public shaming on stuff like this. :) If you find yourself on the top of a list like list, and you feel a bit bad about it, good. Learn from it, push to try more

Re: Excessive inbound bustage

Some exciting statistics on these things if you're interested: http://futurama.theautomatedtester.co.uk/ I'll leave it to you to draw whatever conclusions you want. -Ryan On 4/20/2015 4:54 PM, Aaron Klotz wrote: Do I have terrible timing when it comes to landing patches, or has inbound been

Re: Mozillabuild 2.0 ready for testing

dialog popup saying can't find c:\mozilla-build or somesuch. Maybe there's a path hardcoded somewhere? It's a bit of a footgun since the installer defaults to a non c:\mozilla-build install dir. Thanks very much for making bzexport work! cpearce. On 3/9/2015 2:44 PM, Ryan VanderMeulen wrote

Re: Intent to not fix: Building with gcc-4.6 for Fx38+

On 3/10/2015 10:23 PM, Brian Smith wrote: (2) The trychooser tool should be extended to make it possible to build with GCC 4.7 on any platforms where it is supported, and bootstrap.py be updated to install GCC 4.7 alongside the currently-installed compiler. All Android and B2G JB/KK emulator

Mozillabuild 2.0 ready for testing

For the past many months, I have been working on some major updates to the Mozillabuild package in order to make it more developer-friendly and easily-maintainable in the future. I am proud to say that at this time, it is ready for more widespread testing. The latest test build can be downloaded

Re: PSA: IDL file changes may now be rejected by server-side hook

On 2/20/2015 7:36 PM, Eric Shepherd wrote: Is there any way we could add something that would cause a notification to go out to the MDN writing team if IDL is changed? That could have enormous repercussions on our ability to keep up with doc updates for XPCOM interfaces. Eric Shepherd Sr.

Re: PSA: Support for building with gcc 4.6 has been removed

This has now re-landed and stuck. GCC 4.4 running in automation is officially a thing of the past \m/ -Ryan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: PSA: Support for building with gcc 4.6 has been removed

On 1/8/2015 9:16 PM, Joshua Cranmer  wrote: On 1/6/2015 3:33 PM, Ehsan Akhgari wrote: I just landed bug to remove support for building with Visual C++ 2012 as per the previous dev-platform thread. Trevor Saunders has just landed the patch to de-support gcc 4.4 and 4.5 on mozilla-inbound,

Re: PSA: Support for building with Windows SDK 8.1 removed from Gecko 37

On 1/8/2015 11:56 AM, Joshua Cranmer  wrote: In practice, if you're building infrequently (say, provisioning a VM for Windows or Linux for occasional builds, not primary development), then 4 cores and 4GB of RAM appear to suffice (I've used 4GB for a Linux VM on my laptop and 8GB for a Windows

Re: PSA: Support for building with Windows SDK 8.1 removed from Gecko 37

On 1/7/2015 10:20 PM, Yonggang Luo wrote: Does that means windows xp doesn't support anymore? It has no effect on that, same as how dropping support for all MSVC versions prior to 2013 didn't. -Ryan ___ dev-platform mailing list

PSA: Support for building with Windows SDK 8.1 removed from Gecko 37

This was already implicit by making MSVC2013 the minimum supported compiler (since the 8.1 SDK ships with it anyway), but it's now explicitly been made a hard requirement in the build system as well. Various code that was obviously conditioned on older SDK versions was also cleaned up, but it's

Re: Dropping support for MSVC2012

On 1/1/2015 6:08 PM, Ryan VanderMeulen wrote: Having just filed my fourth MSVC2012 is busted bug since we dropped support for 2010 a few weeks ago, I'm wondering what the point of even supporting 2012 is? Are there any licensing/OS support/etc advantages to keeping it around vs. just leaving

Dropping support for MSVC2012

Having just filed my fourth MSVC2012 is busted bug since we dropped support for 2010 a few weeks ago, I'm wondering what the point of even supporting 2012 is? Are there any licensing/OS support/etc advantages to keeping it around vs. just leaving 2013 as our only supported compiler? Because

Sheriff coverage over the holidays

Just a friendly reminder that over the coming weeks, there will be reduced full-time sheriff coverage due to the holidays and vacations. Please make an effort to keep an eye on your pushes to ensure that any issues are resolved in a timely fashion and minimally impact others. Thanks! -Ryan

Announcing MozillaBuild 1.11.0 Release

I am pleased to announce the final release of MozillaBuild 1.11.0. All users are encouraged to upgrade as soon as possible due to the included Mercurial security fix. http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Important changes since version

  1   2   >