f8f2b26d11f0c6f5058620adc8b3f2633a8448fd: Bug 1377216 - Use substs for determining checkout type; r?glandium draft
Gregory Szorc <gps@mozilla.com> - Fri, 14 Jul 2017 17:22:14 -0700 - rev 610966
Push 69070 by bmo:gps@mozilla.com at Wed, 19 Jul 2017 01:11:03 +0000
Bug 1377216 - Use substs for determining checkout type; r?glandium We now have a variable in config.status for recording the checkout type. These helper functions for determining if we're Mercurial or Git can now be one-liners. As a bonus, we no longer do I/O as part of this function. MozReview-Commit-ID: HT9sbOhDEkf
e50d6f4d3a8123bc62fbcdcb9252d4a1d1d36d0e: Bug 1377216 - Discover version control info in configure; r?glandium draft
Gregory Szorc <gps@mozilla.com> - Tue, 18 Jul 2017 18:07:29 -0700 - rev 610965
Push 69070 by bmo:gps@mozilla.com at Wed, 19 Jul 2017 01:11:03 +0000
Bug 1377216 - Discover version control info in configure; r?glandium For reasons unknown to me, Windows CI is periodically failing to find the Mercurial binary. In addition, we've also reimplemented various VCS logic throughout the build system. There is room to cut down on code complexity by e.g. recording VCS info in configure instead of determining it at run-time. Also, for forensic purposes it is sometimes desirable to know which VCS tool is in use by a build and which version of that tool is being used. This commit adds VCS type detection, binary searching, and version resolution to configure. substs now contains VCS_CHECKOUT_TYPE, HG, and GIT, which can be consulted by downstream consumers. If the Mercurial or Git versions could not be resolved, all variables are not set. Otherwise, VCS_CHECKOUT_TYPE and one of HG or GIT is set. If MOZ_AUTOMATION is set, we require that the VCS info be resolved. This helps prevents weirdness in automation due to unexpected environment configuration. MozReview-Commit-ID: AMLy0Hfx5rD
212f03efaa5d4a10f288ba69711d99f934225949: Bug 1377216 - Accept environment variables to check_cmd_output; r?glandium draft
Gregory Szorc <gps@mozilla.com> - Tue, 18 Jul 2017 18:06:03 -0700 - rev 610964
Push 69070 by bmo:gps@mozilla.com at Wed, 19 Jul 2017 01:11:03 +0000
Bug 1377216 - Accept environment variables to check_cmd_output; r?glandium And include code to work around a bug on older Python versions. MozReview-Commit-ID: 4pBnMQQJOGB
037f7e952f6dd3f7e74d123647502ac29263b878: Bug 1363999 - Add sync metadata to formautofill records. r=markh,lchang draft
Thom Chiovoloni <tchiovoloni@mozilla.com> - Tue, 09 May 2017 15:27:09 +1000 - rev 610963
Push 69069 by bmo:markh@mozilla.com at Wed, 19 Jul 2017 01:07:28 +0000
Bug 1363999 - Add sync metadata to formautofill records. r=markh,lchang This patch lands the metadata and related functions to the ProfileStorage necessary for Sync to function. * New "public" functions which are intended to be used only by Sync: ** pullSyncChanges: Gets metadata about what Sync needs to upload to the server. ** pushSyncChanges: Apply the changes made by Sync. ** resetSync: Reset all Sync metadata, used when Sync is disconnected from a device. ** changeGUID to change the GUID of an item that has no sync metadata. * New optional Sync metdata for a record. Once a record is marked as Syncing, it carries around a new _sync field. Currently this contains only a changeCounter. All records are marked as Syncing once pullSyncChanges is called - after this call, all local records will have Sync metadata. * Changes to tombstones semantics: If an item carries no Sync metadata (ie, hasn't previously been synced), then no tombstone will be left behind when it is deleted. * Many existing functions get an optional {rawData} option, which will include all fields with a leading underscore (_) - which obviously includes this new _sync field - to be returned in the record. * Many existing functions get an optional {sourceSync} option, which indicates Sync itself is making the change. This significantly changes the semantics of some operations (eg, counters will not be incremented, tombstones can be resurrected, etc) MozReview-Commit-ID: 3DjzNiA8buE
baa76ba20e95627be1dc557a64ec43c13f1803d5: Bug 1381957 - Speed up the stop/reload animations based on user feedback. r?sfoster draft
Jared Wein <jwein@mozilla.com> - Tue, 18 Jul 2017 21:01:46 -0400 - rev 610962
Push 69068 by bmo:jaws@mozilla.com at Wed, 19 Jul 2017 01:05:02 +0000
Bug 1381957 - Speed up the stop/reload animations based on user feedback. r?sfoster MozReview-Commit-ID: KEAPr2Y1X3W
537718b5b17c9c355d77094660c0eb624ff4e30f: Bug 1381772 - Add taskcluster jobs to build sccache for automation. r?ted draft
Mike Hommey <mh+mozilla@glandium.org> - Fri, 14 Jul 2017 11:07:40 +0900 - rev 610961
Push 69067 by bmo:mh+mozilla@glandium.org at Wed, 19 Jul 2017 01:01:10 +0000
Bug 1381772 - Add taskcluster jobs to build sccache for automation. r?ted The MinGit tooltool package used for Windows builds comes straight from https://github.com/git-for-windows/git/releases/ This builds the version currently used on automation.
a49b54b9ced7a9ccfd6099f7876e233e82a9f674: Bug 1381770 - Don't use the relengapi proxy for Linux toolchain jobs. r?mshal draft
Mike Hommey <mh+mozilla@glandium.org> - Tue, 18 Jul 2017 16:18:45 +0900 - rev 610960
Push 69067 by bmo:mh+mozilla@glandium.org at Wed, 19 Jul 2017 01:01:10 +0000
Bug 1381770 - Don't use the relengapi proxy for Linux toolchain jobs. r?mshal As the relengapi proxy doesn't appear to be very reliable, let's just use the public releng API, since we only need public artifacts anyways (no need for the relengapi token, which Linux TC workers don't have)
80e666295c1598a87fc320e337b7258d44f4a0b2: Bug 1381770 - In tooltool-download.sh, automatically setup the relengapi authentication file. r?mshal draft
Mike Hommey <mh+mozilla@glandium.org> - Tue, 18 Jul 2017 16:13:26 +0900 - rev 610959
Push 69067 by bmo:mh+mozilla@glandium.org at Wed, 19 Jul 2017 01:01:10 +0000
Bug 1381770 - In tooltool-download.sh, automatically setup the relengapi authentication file. r?mshal
370bbbfa21c201a234eabc06f980f810295b1a6f: Bug 1381770 - In tooltool-download.sh, only use the relengapi proxy when it's configured. r?mshal draft
Mike Hommey <mh+mozilla@glandium.org> - Tue, 18 Jul 2017 16:12:58 +0900 - rev 610958
Push 69067 by bmo:mh+mozilla@glandium.org at Wed, 19 Jul 2017 01:01:10 +0000
Bug 1381770 - In tooltool-download.sh, only use the relengapi proxy when it's configured. r?mshal
3c78c25299fcff56a3ca18d9c485dd25812918bb: Bug 1381770 - Enable multiple download retries in tooltool-download.sh. r?mshal draft
Mike Hommey <mh+mozilla@glandium.org> - Tue, 18 Jul 2017 14:51:04 +0900 - rev 610957
Push 69067 by bmo:mh+mozilla@glandium.org at Wed, 19 Jul 2017 01:01:10 +0000
Bug 1381770 - Enable multiple download retries in tooltool-download.sh. r?mshal The scripts that use tooltool-download.sh don't run regularly, but when they do, they might hit some download problems (the relengapi proxy tends to be rather unreliable for some reason), and in that case, it would be better to retry a few times, like other job types, rather than fail directly.
8792784ce3daa34a291517def7abd09ecfb738a2: Bug 1381770 - Use $WORKSPACE instead of $HOME/workspace in tooltool-download.sh. r?mshal draft
Mike Hommey <mh+mozilla@glandium.org> - Tue, 18 Jul 2017 14:49:05 +0900 - rev 610956
Push 69067 by bmo:mh+mozilla@glandium.org at Wed, 19 Jul 2017 01:01:10 +0000
Bug 1381770 - Use $WORKSPACE instead of $HOME/workspace in tooltool-download.sh. r?mshal All the current users of tooltool-download.sh set $WORKSPACE. This will allow to reuse the script on different types of workers, that don't have $WORKSPACE set to $HOME/workspace, but still have the source in $WORKSPACE/build/src.
8fff22819b8b2e776544ce98f12ead3784cf6753: Bug 1372697 - Consolidate main mozconfig for Linux64; r?glandium draft
Gregory Szorc <gps@mozilla.com> - Tue, 18 Jul 2017 17:51:12 -0700 - rev 610955
Push 69066 by bmo:gps@mozilla.com at Wed, 19 Jul 2017 00:57:27 +0000
Bug 1372697 - Consolidate main mozconfig for Linux64; r?glandium Currently, we have per-channel mozconfigs for many platforms, including Linux64. This creates an explosion of mozconfig variants. In addition, the mechanism by which these mozconfigs are activated is by differing the main mozconfig according to the repo that scheduled the job. This is currently done in mozharness in the branch_specifics.py file. This commit moves us a step closer to doing away with repo-specific mozconfigs by consolidating the per-repo/channel mozconfig differences into a single file. The "nightly" mozconfig has been renamed to "main." Inside, it has grown conditional branches that take into account the recently-introduced MOZ_BUILD_CHANNEL environment variable to incorporate the logic from the now-deleted "beta" and "release" mozconfigs. References to the old mozconfigs have been purged or updated as necessary. It's worth noting that the consolidation of the mozconfigs combined with MOZ_BUILD_CHANNEL dictating behavior means that certain mozconfigs previously including the "nightly" mozconfig (such as opt-dmd) will now inherit the "beta" or "release" channel configuration instead of the "nightly" one. This is arguably a feature, not a bug. However, it will likely result in unintentional fallout. MozReview-Commit-ID: LJHQTLyBjxE
a763b77f455072094165d97a2601c20e7c700f75: Bug 1372697 - Export MOZ_BUILD_CHANNEL to build tasks; r?glandium draft
Gregory Szorc <gps@mozilla.com> - Tue, 18 Jul 2017 17:49:43 -0700 - rev 610954
Push 69066 by bmo:gps@mozilla.com at Wed, 19 Jul 2017 00:57:27 +0000
Bug 1372697 - Export MOZ_BUILD_CHANNEL to build tasks; r?glandium Currently, there are a number of places that vary what is built by the repository being built. This behavior is sub-optimal because it makes it difficult to trigger a build configuration outside of a well-defined repository. This commit starts the process of abstracting away these repo-specific differences by introducing a new environment variable: MOZ_BUILD_CHANNEL. This variable defines the channel configuration that we want to build. Right now the variable is populated from the source repository ("project" in taskgraph parlance). But in the future we can change how it is set. The important thing is that the build system can react to the presence of the variable to take conditional actions based on the active channel configuration. The utility of this will be demonstrated in subsequent commits. MozReview-Commit-ID: L9jJQcPCXL8
82eedb4427b7442beda009805581572badc0d675: Bug 1374477 - Photon SVG changes for page action panel. r?mikedeboer draft
Drew Willcoxon <adw@mozilla.com> - Tue, 18 Jul 2017 17:48:38 -0700 - rev 610953
Push 69065 by dwillcoxon@mozilla.com at Wed, 19 Jul 2017 00:50:30 +0000
Bug 1374477 - Photon SVG changes for page action panel. r?mikedeboer MozReview-Commit-ID: 5oGeJPT8j3f
339aabfca0f10ddf1d408aa717a1fbac18e5ec5d: Bug 1374477 - Update consumers of Photon page action panel for changed identifiers. r?mikedeboer draft
Drew Willcoxon <adw@mozilla.com> - Tue, 18 Jul 2017 17:48:35 -0700 - rev 610952
Push 69065 by dwillcoxon@mozilla.com at Wed, 19 Jul 2017 00:50:30 +0000
Bug 1374477 - Update consumers of Photon page action panel for changed identifiers. r?mikedeboer MozReview-Commit-ID: 1skE8YJaqA7
c5a275dfaa2a50312aea6389884faf18aa0797aa: Bug 1374477 - Update Photon page action panel CSS. r?mikedeboer draft
Drew Willcoxon <adw@mozilla.com> - Tue, 18 Jul 2017 17:48:33 -0700 - rev 610951
Push 69065 by dwillcoxon@mozilla.com at Wed, 19 Jul 2017 00:50:30 +0000
Bug 1374477 - Update Photon page action panel CSS. r?mikedeboer MozReview-Commit-ID: K5vAkfK1Skr
b32dda2dd2bdac87cf5d2b8ef9298160c0b81fa3: Bug 1374477 - Remove page actions from browser.xul. r?mikedeboer draft
Drew Willcoxon <adw@mozilla.com> - Tue, 18 Jul 2017 17:48:30 -0700 - rev 610950
Push 69065 by dwillcoxon@mozilla.com at Wed, 19 Jul 2017 00:50:30 +0000
Bug 1374477 - Remove page actions from browser.xul. r?mikedeboer MozReview-Commit-ID: 5nlXfKOx3Aq
52bcc4032d4bcd107cb4fd5286dd04dfeda2f88a: Bug 1374477 - Add browser-pageActions.js for Photon page actions. r?mikedeboer draft
Drew Willcoxon <adw@mozilla.com> - Tue, 18 Jul 2017 17:48:27 -0700 - rev 610949
Push 69065 by dwillcoxon@mozilla.com at Wed, 19 Jul 2017 00:50:30 +0000
Bug 1374477 - Add browser-pageActions.js for Photon page actions. r?mikedeboer MozReview-Commit-ID: DUl7WlSnk4k
4df415bbb875fa3e405090e0e938a4faffeebf98: Bug 1374477 - Add PageActions.jsm for Photon page actions. r?mikedeboer draft
Drew Willcoxon <adw@mozilla.com> - Tue, 18 Jul 2017 17:48:17 -0700 - rev 610948
Push 69065 by dwillcoxon@mozilla.com at Wed, 19 Jul 2017 00:50:30 +0000
Bug 1374477 - Add PageActions.jsm for Photon page actions. r?mikedeboer MozReview-Commit-ID: ASMQlPX5t1i
9c977f6435d92d62a828fbe17c7dad6095b6441d: Bug 1375816 - Part 4: VRController displayId attribute testcase; r?kip draft
Daosheng Mu <daoshengmu@gmail.com> - Fri, 14 Jul 2017 17:08:15 +0800 - rev 610947
Push 69064 by bmo:dmu@mozilla.com at Wed, 19 Jul 2017 00:44:08 +0000
Bug 1375816 - Part 4: VRController displayId attribute testcase; r?kip MozReview-Commit-ID: KkMXsTDRnQO
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip