Acc mercurial Mercurial > mozilla-central / search summary | shortlog | changelog | pushlog | graph | tags | bookmarks | branches | files | zip | help searching for Firefox 223 Linux 80ffb2b569bd2f12127bacecd065db364f497cb8: Bug 1802233 - target_is_linux_or_wasi was not meant to include Android. r=firefox-build-system-reviewers,ahochheiden diff browse Mike Hommey <[email protected]> - Thu, 24 Nov 2022 00:46:13 +0000 - rev 643438 Push 40429 by [email protected] at Thu, 24 Nov 2022 21:26:38 +0000 Bug 1802233 - target_is_linux_or_wasi was not meant to include Android. r=firefox-build-system-reviewers,ahochheiden To avoid the confusion with target_is_linux meaning linux+android, we rename target_is_linux to target_has_linux_kernel. Naming is hard. Differential Revision: https://phabricator.services.mozilla.com/D162913 455d5db0d4bdc34bd4b75be5e853b6506c46f649: Bug 1773223 - Make the GN processor an independent script. r=firefox-build-system-reviewers,mjf,ahochheiden diff browse Mike Hommey <[email protected]> - Tue, 21 Jun 2022 02:30:37 +0000 - rev 621540 Push 39877 by [email protected] at Tue, 21 Jun 2022 09:32:33 +0000 Bug 1773223 - Make the GN processor an independent script. r=firefox-build-system-reviewers,mjf,ahochheiden The way the processor works currently is that it relies on two different build backends, one of which produces json files for specific configurations, and the other which produces moz.build files from the aggregate of all those configs. Each of these json files is huge, and we actually don't have enough to support all the platforms we're supposed to be supporting. Adding more files is not enticing. Now that we've made the first step described above work in a single pass on a single machine (as opposed to multiple passes on multiple machines previously), we can actually merge both steps and avoid producing the intermediate json files altogether. This will allow to add more configurations without having to worry about the weight of those files. And because this all doesn't need to depend on having the first step hooked up in the build system, we make the whole an independent script rather than a build backend. Differential Revision: https://phabricator.services.mozilla.com/D149210 11f3375a4a704158a253195a15d397c7f8927598: Bug 1773223 - Make the GN processor an independent script. r=firefox-build-system-reviewers,mjf,ahochheiden diff browse Mike Hommey <[email protected]> - Mon, 20 Jun 2022 22:04:12 +0000 - rev 621522 Push 39875 by [email protected] at Tue, 21 Jun 2022 03:57:01 +0000 Bug 1773223 - Make the GN processor an independent script. r=firefox-build-system-reviewers,mjf,ahochheiden The way the processor works currently is that it relies on two different build backends, one of which produces json files for specific configurations, and the other which produces moz.build files from the aggregate of all those configs. Each of these json files is huge, and we actually don't have enough to support all the platforms we're supposed to be supporting. Adding more files is not enticing. Now that we've made the first step described above work in a single pass on a single machine (as opposed to multiple passes on multiple machines previously), we can actually merge both steps and avoid producing the intermediate json files altogether. This will allow to add more configurations without having to worry about the weight of those files. And because this all doesn't need to depend on having the first step hooked up in the build system, we make the whole an independent script rather than a build backend. Differential Revision: https://phabricator.services.mozilla.com/D149210 2b263cd7649205796467a480e2d96e061f58490c: Bug 1773223 - Generate webrtc moz.builds for all platforms at once. r=mjf,firefox-build-system-reviewers,ahochheiden diff browse Mike Hommey <[email protected]> - Mon, 20 Jun 2022 21:50:57 +0000 - rev 621517 Push 39875 by [email protected] at Tue, 21 Jun 2022 03:57:01 +0000 Bug 1773223 - Generate webrtc moz.builds for all platforms at once. r=mjf,firefox-build-system-reviewers,ahochheiden The current script requires to be run on 4 different host platforms each of which would handle a subset of a total of 32 mozconfigs. That is not sustainable, and there are already missing configs that break tier-3 platforms. This replaces the current setup with one that handles all platforms in one go, although we still keep the internal sequence of GcConfigGen -> fixup_json -> GnMozbuildWriter. The downside is that because this relies on the upstream webrtc build system supporting cross-compilation, and that it actively rejects some configurations, we need some local hacks to make it work on Linux and Mac, but for now, we have to leave out Windows, which requires more work. For some reason, that removes some duplicated include directories in the json files, which moves things a little in one moz.build file. We also remove the mozconfigs we don't use anymore. Differential Revision: https://phabricator.services.mozilla.com/D149205 5e1c0d1d401873393c549ee0cd7cd8e0323ce7bf: Bug 1773223 - Make the GN processor an independent script. r=firefox-build-system-reviewers,mjf,ahochheiden diff browse Mike Hommey <[email protected]> - Mon, 20 Jun 2022 20:58:30 +0000 - rev 621508 Push 39875 by [email protected] at Tue, 21 Jun 2022 03:57:01 +0000 Bug 1773223 - Make the GN processor an independent script. r=firefox-build-system-reviewers,mjf,ahochheiden The way the processor works currently is that it relies on two different build backends, one of which produces json files for specific configurations, and the other which produces moz.build files from the aggregate of all those configs. Each of these json files is huge, and we actually don't have enough to support all the platforms we're supposed to be supporting. Adding more files is not enticing. Now that we've made the first step described above work in a single pass on a single machine (as opposed to multiple passes on multiple machines previously), we can actually merge both steps and avoid producing the intermediate json files altogether. This will allow to add more configurations without having to worry about the weight of those files. And because this all doesn't need to depend on having the first step hooked up in the build system, we make the whole an independent script rather than a build backend. Differential Revision: https://phabricator.services.mozilla.com/D149210 f349d4ad00884a6ac6f933a9fccc282bdc4de6fa: Bug 1773223 - Generate webrtc moz.builds for all platforms at once. r=mjf,firefox-build-system-reviewers,ahochheiden diff browse Mike Hommey <[email protected]> - Mon, 20 Jun 2022 20:58:27 +0000 - rev 621503 Push 39875 by [email protected] at Tue, 21 Jun 2022 03:57:01 +0000 Bug 1773223 - Generate webrtc moz.builds for all platforms at once. r=mjf,firefox-build-system-reviewers,ahochheiden The current script requires to be run on 4 different host platforms each of which would handle a subset of a total of 32 mozconfigs. That is not sustainable, and there are already missing configs that break tier-3 platforms. This replaces the current setup with one that handles all platforms in one go, although we still keep the internal sequence of GcConfigGen -> fixup_json -> GnMozbuildWriter. The downside is that because this relies on the upstream webrtc build system supporting cross-compilation, and that it actively rejects some configurations, we need some local hacks to make it work on Linux and Mac, but for now, we have to leave out Windows, which requires more work. For some reason, that removes some duplicated include directories in the json files, which moves things a little in one moz.build file. We also remove the mozconfigs we don't use anymore. Differential Revision: https://phabricator.services.mozilla.com/D149205 8281fa0ead0ed4d3a44405bba8a12fc218d9dd03: Bug 1773223 - Turn gn into local toolchains. r=firefox-build-system-reviewers,ahochheiden diff browse Mike Hommey <[email protected]> - Wed, 15 Jun 2022 07:06:06 +0000 - rev 620932 Push 39854 by [email protected] at Wed, 15 Jun 2022 15:46:59 +0000 Bug 1773223 - Turn gn into local toolchains. r=firefox-build-system-reviewers,ahochheiden - Because we don't have a native arm64 mac one, alias the x86_64 one. - Because we always compress with zstd, don't pretend the main script has any power on the compression (which was wrong for Windows). Differential Revision: https://phabricator.services.mozilla.com/D149204 442c6e998e90a8a7fa9a7928ebf24f001f1563bd: Backed out 3 changesets (bug 1752232, bug 1734722) for causing spider-monkey failures. CLOSED TREE diff browse Sandor Molnar <[email protected]> - Mon, 31 Jan 2022 23:45:44 +0200 - rev 606056 Push 39223 by [email protected] at Tue, 01 Feb 2022 09:39:42 +0000 Backed out 3 changesets (bug 1752232, bug 1734722) for causing spider-monkey failures. CLOSED TREE Backed out changeset 319186f8024a (bug 1752232) Backed out changeset 0a448a73bc66 (bug 1734722) Backed out changeset e684ad3cd11a (bug 1734722) 29d7e91fe7216c37639b4a836c83bdb20b03a28c: Bug 1725125 - Make a hybrid build system combining non-unified with unified r=firefox-build-system-reviewers,mhentges,glandium diff browse Andi-Bogdan Postelnicu <[email protected]> - Wed, 25 Aug 2021 10:46:18 +0000 - rev 589879 Push 38735 by [email protected] at Wed, 25 Aug 2021 15:39:54 +0000 Bug 1725125 - Make a hybrid build system combining non-unified with unified r=firefox-build-system-reviewers,mhentges,glandium By hybrid unified system we understand a system that encapsulates modules that are built in the unified mode but also other modules, like `dom/Animation`, as an example, in the non unified environment. This approach is desirable since we already have most of the modules transitioned to the non unified system but there are still some that are not yet compatible, but in the long term this will be done by each module owner and can be also tested locally using the build system. If a module can't be built outside the unified method it's `moz.build` config file needs to have `REQUIRES_UNIFIED_BUILD = False` To also enable this we need to have a flag from `mozconfig`, like: ``` ac_add_options --disable-unified-build ``` Differential Revision: https://phabricator.services.mozilla.com/D122328 3e615329b0a3a5aa2029c68dd84bfd5eb2acaeda: Bug 1725145 - Preparation for the hybrid build env. r=necko-reviewers,firefox-build-system-reviewers,valentin,glandium diff browse Andi-Bogdan Postelnicu <[email protected]> - Wed, 25 Aug 2021 10:46:17 +0000 - rev 589878 Push 38735 by [email protected] at Wed, 25 Aug 2021 15:39:54 +0000 Bug 1725145 - Preparation for the hybrid build env. r=necko-reviewers,firefox-build-system-reviewers,valentin,glandium Automatically generated path that adds flag `REQUIRES_UNIFIED_BUILD = True` to `moz.build` when the module governed by the build config file is not buildable outside on the unified environment. This needs to be done in order to have a hybrid build system that adds the possibility of combing unified build components with ones that are built outside of the unified eco system. Differential Revision: https://phabricator.services.mozilla.com/D122345 7e61e2eb9045117844ea7df96f0ba94eed4bd4ad: Bug 1692179 [wpt PR 27590] - Revert "[TablesNG] Implement column track merging", a=testonly diff browse Thiemo Nagel <[email protected]> - Thu, 11 Feb 2021 16:50:24 +0000 - rev 567271 Push 38199 by [email protected] at Fri, 12 Feb 2021 21:51:52 +0000 Bug 1692179 [wpt PR 27590] - Revert "[TablesNG] Implement column track merging", a=testonly Automatic update from web-platform-tests Revert "[TablesNG] Implement column track merging" This reverts commit 2dadda0cccbda46a2fffe23e8c607e88f4d45394. Reason for revert: Suspected cause of paint/tables/huge-table-composited-scroll-collapsed-borders.html failures https://ci.chromium.org/ui/p/chromium/builders/ci/WebKit%20Linux%20ASAN/22054 Original change's description: > [TablesNG] Implement column track merging > > One the a11y requirements was that tables should do track merging. > I've skipped implementing this initially because there was major > disagreement about what to do. > > This implementation follows the standard. > Columns defined by TD or COL are merged for table-layout:auto, > and not merged for table-layout:fixed. > > Legacy did not follow the standard for columns defined by TDs: > they were always merged. Firefox implementation was closer to > standard, but sometimes buggy. > > This changes results of some tests. Almost all of them are because > "TablesNG is more standards compliant", and new renderings match > FF. > > There is disagreement about treatment of empty rows between > FF and TablesNGNG. > > external/wpt/css/css-tables/html5-table-formatting-1.html > external/wpt/css/css-tables/html5-table-formatting-2.html > > The rest of the changes render better, just like FF. > > Two new tests have been added: > wpt/css/css-tables/column-track-merging.html > tests the standard. > > accessibility/table-column-track-merging.html > tests Chrome's a11y API. > > Change-Id: Ia222351f7c500963ace556d76c26fcefb1df24e1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2670193 > Commit-Queue: Aleks Totic <[email protected]> > Reviewed-by: Ian Kilpatrick <[email protected]> > Reviewed-by: David Grogan <[email protected]> > Cr-Commit-Position: refs/heads/master@{#852958} [email protected],[email protected],[email protected],[email protected] Change-Id: Id914684949be4eb6196a850bb1168d25872346ef No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2690334 Reviewed-by: Thiemo Nagel <[email protected]> Commit-Queue: Thiemo Nagel <[email protected]> Cr-Commit-Position: refs/heads/master@{#853075} -- wpt-commits: 496c290543d0572ec532b092a3b2e7fe03381293 wpt-pr: 27590 1844991b6ebd33847b783338e2b6c629738e8ed0: Bug 1692179 [wpt PR 27590] - Revert "[TablesNG] Implement column track merging", a=testonly diff browse Thiemo Nagel <[email protected]> - Thu, 11 Feb 2021 16:50:24 +0000 - rev 567184 Push 38198 by [email protected] at Fri, 12 Feb 2021 16:21:58 +0000 Bug 1692179 [wpt PR 27590] - Revert "[TablesNG] Implement column track merging", a=testonly Automatic update from web-platform-tests Revert "[TablesNG] Implement column track merging" This reverts commit 2dadda0cccbda46a2fffe23e8c607e88f4d45394. Reason for revert: Suspected cause of paint/tables/huge-table-composited-scroll-collapsed-borders.html failures https://ci.chromium.org/ui/p/chromium/builders/ci/WebKit%20Linux%20ASAN/22054 Original change's description: > [TablesNG] Implement column track merging > > One the a11y requirements was that tables should do track merging. > I've skipped implementing this initially because there was major > disagreement about what to do. > > This implementation follows the standard. > Columns defined by TD or COL are merged for table-layout:auto, > and not merged for table-layout:fixed. > > Legacy did not follow the standard for columns defined by TDs: > they were always merged. Firefox implementation was closer to > standard, but sometimes buggy. > > This changes results of some tests. Almost all of them are because > "TablesNG is more standards compliant", and new renderings match > FF. > > There is disagreement about treatment of empty rows between > FF and TablesNGNG. > > external/wpt/css/css-tables/html5-table-formatting-1.html > external/wpt/css/css-tables/html5-table-formatting-2.html > > The rest of the changes render better, just like FF. > > Two new tests have been added: > wpt/css/css-tables/column-track-merging.html > tests the standard. > > accessibility/table-column-track-merging.html > tests Chrome's a11y API. > > Change-Id: Ia222351f7c500963ace556d76c26fcefb1df24e1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2670193 > Commit-Queue: Aleks Totic <[email protected]> > Reviewed-by: Ian Kilpatrick <[email protected]> > Reviewed-by: David Grogan <[email protected]> > Cr-Commit-Position: refs/heads/master@{#852958} [email protected],[email protected],[email protected],[email protected] Change-Id: Id914684949be4eb6196a850bb1168d25872346ef No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2690334 Reviewed-by: Thiemo Nagel <[email protected]> Commit-Queue: Thiemo Nagel <[email protected]> Cr-Commit-Position: refs/heads/master@{#853075} -- wpt-commits: 496c290543d0572ec532b092a3b2e7fe03381293 wpt-pr: 27590 549c6ecc1c215c8bcc04452396cc84dbeafb7bdb: Merge mozilla-central to inbound. a=merge CLOSED TREE diff browse Gurzau Raul <[email protected]> - Tue, 10 Sep 2019 06:32:42 +0300 - rev 492436 Push 36556 by [email protected] at Tue, 10 Sep 2019 09:56:13 +0000 Merge mozilla-central to inbound. a=merge CLOSED TREE 43376e0c35631124193d304daeea1c557d487a8a: Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium diff browse Sylvestre Ledru <[email protected]> - Sun, 10 Mar 2019 15:29:41 +0000 - rev 463408 Push 35676 by [email protected] at Sun, 10 Mar 2019 21:40:03 +0000 Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium Differential Revision: https://phabricator.services.mozilla.com/D21459 362cf2e57ed2851c113a00d358207e27aded9cc5: Backed out changeset e908fbc7b930 (bug 1531176) for bc failures at browser_Troubleshoot.js. CLOSED TREE diff browse Brindusan Cristian <[email protected]> - Fri, 08 Mar 2019 00:07:56 +0200 - rev 463025 Push 35665 by [email protected] at Fri, 08 Mar 2019 09:39:15 +0000 Backed out changeset e908fbc7b930 (bug 1531176) for bc failures at browser_Troubleshoot.js. CLOSED TREE e908fbc7b9302f680b0bc3924d49c0f027739c9d: Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium diff browse Sylvestre Ledru <[email protected]> - Thu, 07 Mar 2019 21:05:32 +0000 - rev 463021 Push 35665 by [email protected] at Fri, 08 Mar 2019 09:39:15 +0000 Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium Differential Revision: https://phabricator.services.mozilla.com/D21459 12e0e7785e853ea9ec95d579afdbc05487d84d37: Backed out changeset 3fb6c01dd2b0 (bug 1531176) for causing gradle toolchain bustage CLOSED TREE diff browse Ciure Andrei <[email protected]> - Thu, 07 Mar 2019 14:23:03 +0200 - rev 462862 Push 35661 by [email protected] at Thu, 07 Mar 2019 21:56:20 +0000 Backed out changeset 3fb6c01dd2b0 (bug 1531176) for causing gradle toolchain bustage CLOSED TREE 3fb6c01dd2b0e1d4e8e0af450b831048d9274456: Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium diff browse Sylvestre Ledru <[email protected]> - Thu, 07 Mar 2019 12:04:53 +0000 - rev 462861 Push 35661 by [email protected] at Thu, 07 Mar 2019 21:56:20 +0000 Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium Differential Revision: https://phabricator.services.mozilla.com/D21459 e9b5af495b6bf00a4c664bf47ea1e7163128e22f: Backed out changeset 0f2b9b0bf9b9 (bug 1531176) for google-geolocation-api-keyfile build bustages CLOSED TREE diff browse Ciure Andrei <[email protected]> - Thu, 07 Mar 2019 13:58:33 +0200 - rev 462858 Push 35661 by [email protected] at Thu, 07 Mar 2019 21:56:20 +0000 Backed out changeset 0f2b9b0bf9b9 (bug 1531176) for google-geolocation-api-keyfile build bustages CLOSED TREE 0f2b9b0bf9b966210b3e0dd6709cde35e33558a6: Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium diff browse Sylvestre Ledru <[email protected]> - Thu, 07 Mar 2019 11:31:18 +0000 - rev 462856 Push 35661 by [email protected] at Thu, 07 Mar 2019 21:56:20 +0000 Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium Differential Revision: https://phabricator.services.mozilla.com/D21459 mozilla-central Deployed from a8f3b23c660e at 2023-03-13T16:25:26Z. RSS Atomesos directos de teclado para las búsquedas