searching for reviewer(glandium)
fb01125329bf28e56389894039be17cd5ab6f622: Bug 1562686 - revert remaining unnecessary bit of bug 1187245; r=glandium a=tomprince
Dustin J. Mitchell <dustin@mozilla.com> - Fri, 23 Aug 2019 12:32:02 +0000 - rev 451324
Push 502 by mozilla@hocat.ca at Wed, 18 Sep 2019 18:05:10 +0000
Bug 1562686 - revert remaining unnecessary bit of bug 1187245; r=glandium a=tomprince Differential Revision: https://phabricator.services.mozilla.com/D42644
e37f559cf5236bbcc33c80ee1c232689c7aa6f0d: Bug 1516325. r=glandium, a=lizzard
Jed Davis <jld@mozilla.com> - Thu, 18 Apr 2019 16:11:21 -0400 - rev 451116
Push 393 by ryanvm@gmail.com at Thu, 18 Apr 2019 20:14:21 +0000
Bug 1516325. r=glandium, a=lizzard Differential Revision: https://phabricator.services.mozilla.com/D22638
e52e5cbf552da863cdf5b824913a1679717c863c: Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium a=RyanVM
Sylvestre Ledru <sledru@mozilla.com> - Sun, 10 Mar 2019 15:29:41 +0000 - rev 451063
Push 365 by archaeopteryx@coole-files.de at Mon, 11 Mar 2019 17:39:35 +0000
Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium a=RyanVM Differential Revision: https://phabricator.services.mozilla.com/D21459
01b634d28203ce7be051454f700be3d52af08494: Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium a=RyanVM
Sylvestre Ledru <sledru@mozilla.com> - Sun, 10 Mar 2019 15:29:41 +0000 - rev 451061
Push 363 by archaeopteryx@coole-files.de at Mon, 11 Mar 2019 15:19:56 +0000
Bug 1531176 - Split the Google key management between gls and safe browsing r=glandium a=RyanVM Differential Revision: https://phabricator.services.mozilla.com/D21459
b732dac3ca9a76fa0ee9cb7e66156a86b1089d60: Bug 1492664 - update diffoscope tasks to use TASKCLUSTER_ROOT_URL; r=glandium
Dustin J. Mitchell <dustin@mozilla.com> - Tue, 02 Oct 2018 15:52:28 +0000 - rev 451011
Push 360 by mozilla@hocat.ca at Mon, 11 Mar 2019 02:11:57 +0000
Bug 1492664 - update diffoscope tasks to use TASKCLUSTER_ROOT_URL; r=glandium
85993c8f4ce14bd75c94035e16d8cf00d6919876: Bug 1492664 - update libdmg-hfsplus to use TASKCLUSTER_ROOT_URL; r=glandium
Dustin J. Mitchell <dustin@mozilla.com> - Mon, 10 Dec 2018 20:14:52 +0000 - rev 451009
Push 360 by mozilla@hocat.ca at Mon, 11 Mar 2019 02:11:57 +0000
Bug 1492664 - update libdmg-hfsplus to use TASKCLUSTER_ROOT_URL; r=glandium
5782520e2bf99476efd2c91bbfa4bffbf4c6c584: Bug 1492664 - use {artifact-reference: ..} in diffoscope; r=glandium
Dustin J. Mitchell <dustin@mozilla.com> - Thu, 13 Dec 2018 02:14:52 +0000 - rev 451004
Push 360 by mozilla@hocat.ca at Mon, 11 Mar 2019 02:11:57 +0000
Bug 1492664 - use {artifact-reference: ..} in diffoscope; r=glandium
a435caff108e8a724bdc2a38e85442311c25c940: Bug 1492664 - set TASKCLUSTER_ROOT_URL and TASKCLUSTER_PROXY_URL; r=tomprince,glandium
Dustin J. Mitchell <dustin@mozilla.com> - Tue, 25 Sep 2018 20:18:19 +0000 - rev 451000
Push 360 by mozilla@hocat.ca at Mon, 11 Mar 2019 02:11:57 +0000
Bug 1492664 - set TASKCLUSTER_ROOT_URL and TASKCLUSTER_PROXY_URL; r=tomprince,glandium Eventually, workers will provide these variables directly (https://bugzilla.mozilla.org/show_bug.cgi?id=1460015). But for now, this ensures that TASKCLUSTER_ROOT_URL is set everywhere in production, and TASKCLUSTER_PROXY_URL is set wherever the proxy is active. The taskgraph Taskcluster utils module gets a `get_root_url()` that gets the root URL for the current run, either from an environment variable in production or, on the command line, defaulting to https://taskcluster.net for user convenience. When the production instance's URL changes, we can simply change that default. Other changes to use this function are reserved for later commits. This changes the docker build process propagate TASKCLUSTER_ROOT_URL into the docker images where necessary (using %ARG), specifically to create URLs for debian repo paths.
b48379043d27c71518be4dc002884fe0566c70de: Bug 1513320 - SQLite package backport for Debian 7; r=glandium
Gregory Szorc <gps@mozilla.com> - Wed, 12 Dec 2018 22:11:59 +0000 - rev 450987
Push 360 by mozilla@hocat.ca at Mon, 11 Mar 2019 02:11:57 +0000
Bug 1513320 - SQLite package backport for Debian 7; r=glandium The SQLite in Debian 7 (3.7.13) lacks support for common table expressions (the WITH keyword), which was introduced in SQLite 3.8.3. The Mercurial SQLite storage backend currently relies on CTEs. Even if a future Mercurial doesn't require CTE, it is likely that it will still use CTE if available for performance reasons. So, it is in our best interest to give Mercurial access to a modern SQLite. Plus, using a modern SQLite and avoiding potential bugs in old versions seems prudent. This commit introduces a SQLite package backport for Debian 7 so we can use the new SQLite feature. We had to minimally patch the build to work with an older version of TCL that isn't using multiarch. I observed libsqlite3 being installed as part of building various other packages (such as Python). I initially added the package as a dependency so packages would be built against a more modern SQLite. But glandium doesn't believe it matters, since nothing should be doing build-time feature detection. Python is the most important downstream package (since Mercurial uses its SQLite). I audited the CPython build system and did not see any build-time SQLite feature detection or version sniffing. So I think we'll be fine building against an older SQLite. Differential Revision: https://phabricator.services.mozilla.com/D14194
6d17a75a4abcc0ef649046154c1b2e5dfb1b8f72: Bug 1531655 - Emit a configure error if rustc version >= 1.33 and --enable-rust-simd used. r=glandium a=RyanVM
Henri Sivonen <hsivonen@hsivonen.fi> - Mon, 04 Mar 2019 21:36:24 +0100 - rev 450951
Push 349 by archaeopteryx@coole-files.de at Mon, 04 Mar 2019 20:49:55 +0000
Bug 1531655 - Emit a configure error if rustc version >= 1.33 and --enable-rust-simd used. r=glandium a=RyanVM
6be34dffbc7432b5a0598846eaba1bf99fa61350: Bug 1471132 - Handle 3-column nm/readelf output in check_binary. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Wed, 09 Jan 2019 01:26:39 -0600 - rev 450845
Push 301 by jcristau@mozilla.com at Thu, 17 Jan 2019 14:20:19 +0000
Bug 1471132 - Handle 3-column nm/readelf output in check_binary. r=glandium, a=jcristau This patch backports only one small part of 1471132 to handle certain types of nm/readelf output.
750ac3b5b7403d4a7438d66077bfdb3c419e4432: Bug 1481633 Resolve kPStaticModules undefined symbols in MinGW Clang. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Tue, 11 Sep 2018 03:20:06 +0000 - rev 450843
Push 301 by jcristau@mozilla.com at Thu, 17 Jan 2019 14:20:19 +0000
Bug 1481633 Resolve kPStaticModules undefined symbols in MinGW Clang. r=glandium, a=jcristau clang can handle MSVC-like codepaths generally, so we want to use those when building with clang for Windows. So we switch _MSC_VER over to _WIN32 to pick up those codepaths when compiling for Windows with clang. Additionally, we relax the ordering of sections for the same scenario. Note that we do need to tell clang to use -fms-extensions with the MSVC code, we do that in the mingw clang build job patch. Differential Revision: https://phabricator.services.mozilla.com/D3526
8a49ed95c148deade0eb0a022ac132359de8a403: Bug 1473291 - handle valueless dynamic section entries; r=glandium, a=jcristau
Nathan Froyd <froydnj@mozilla.com> - Wed, 04 Jul 2018 20:51:25 -0400 - rev 450839
Push 301 by jcristau@mozilla.com at Thu, 17 Jan 2019 14:20:19 +0000
Bug 1473291 - handle valueless dynamic section entries; r=glandium, a=jcristau Some dynamic entry types, like DT_BIND_NOW, are printed without a value by readelf. Handle such types gracefully.
027887b2d74e42bc054e085455b449ee3cc4f65a: Bug 1519209 - Disable NSS_ALLOW_SSLKEYLOGFILE in beta and release. r=glandium, a=RyanVM
Eric Rahm <erahm@mozilla.com> - Thu, 10 Jan 2019 13:14:41 -0800 - rev 450834
Push 299 by ryanvm@gmail.com at Mon, 14 Jan 2019 13:44:32 +0000
Bug 1519209 - Disable NSS_ALLOW_SSLKEYLOGFILE in beta and release. r=glandium, a=RyanVM This disables NSS_ALLOW_SSLKEYLOGFILE in beta in release in order to avoid shutdown hangs until the NSS project has time to fix the root cause of the issue.
84b3320e3c797e2ba1d4c4a6ddb2d777c39af161: Bug 1498640 - deploy latest image_builder image r=glandium
Dustin J. Mitchell <dustin@mozilla.com> - Wed, 31 Oct 2018 23:02:42 +0000 - rev 450780
Push 287 by mozilla@hocat.ca at Fri, 04 Jan 2019 18:54:41 +0000
Bug 1498640 - deploy latest image_builder image r=glandium This uses the latest image_builder image (on docker hub) to build even the image_builder image. The change to `docker.py` handles a new API response (`aux`) from the Docker daemon. It's unclear what this key means, but displaying it is simple. Differential Revision: https://phabricator.services.mozilla.com/D8441
31d3a5d3a2e7e62b2b8031b01b057f7becb181bb: Bug 1434316 - Add 64 Bit Windows Build Targets. r=glandium, a=RyanVM
Tom Ritter <tom@mozilla.com> - Mon, 03 Dec 2018 15:16:43 -0600 - rev 450544
Push 271 by ryanvm@gmail.com at Thu, 13 Dec 2018 14:27:45 +0000
Bug 1434316 - Add 64 Bit Windows Build Targets. r=glandium, a=RyanVM
361aba6e9e4203797dc59d701590d20677d6e298: Bug 1434316 - Bump MinGW version. r=glandium, a=RyanVM
Tom Ritter <tom@mozilla.com> - Fri, 07 Dec 2018 16:39:22 -0600 - rev 450543
Push 271 by ryanvm@gmail.com at Thu, 13 Dec 2018 14:27:45 +0000
Bug 1434316 - Bump MinGW version. r=glandium, a=RyanVM
90efe082fa62a882e8a4e16ef0b668c055fbebf0: Bug 1434316 - Add 64 Bit Windows Build Targets. r=glandium, a=RyanVM
Tom Ritter <tom@mozilla.com> - Fri, 07 Dec 2018 16:39:02 -0600 - rev 450542
Push 271 by ryanvm@gmail.com at Thu, 13 Dec 2018 14:27:45 +0000
Bug 1434316 - Add 64 Bit Windows Build Targets. r=glandium, a=RyanVM
a23dce703d2b616e678f7a72967075f90d650032: Bug 1467605 - Disable processing of fetch dependencies; r=glandium a=tomprince
Gregory Szorc <gps@mozilla.com> - Thu, 07 Jun 2018 23:05:58 +0000 - rev 450488
Push 247 by mozilla@hocat.ca at Fri, 23 Nov 2018 22:37:38 +0000
Bug 1467605 - Disable processing of fetch dependencies; r=glandium a=tomprince 90dca0906337 accidentally broke `mach artifact toolchain --from-build` because that code is attempting to load toolchain tasks in isolation. The new "use_fetches" transform added to toolchain tasks requires that "fetch" tasks are already processed and their references are available to toolchain tasks. This commit adds a mechanism to effectively disable the "use_fetches" transform when called by `mach artifact toolchain`. It is a hack. I suspect future planned work around artifacts/fetches will necessitate additional changes to the `mach artifact toolchain` code. But this can be deferred to a later day: this commit unbusts `mach artifact toolchain` and isn't super hacky, so it seems more reasonable than backing out fetch tasks completely. Differential Revision: https://phabricator.services.mozilla.com/D1588
b1ece767c018300c56363f030f10cfc81516f4ba: Bug 1445943 - Add Enterprise Policy support for macOS to ESR. This includes patches in bug 1445943, bug 1497408, bug 1497948, bug 1498032. r=mstange,felipe,glandium,spohl, a=lizzard
Stephen A Pohl <spohl.mozilla.bugs@gmail.com> - Tue, 20 Nov 2018 02:48:00 -0500 - rev 450486
Push 246 by ryanvm@gmail.com at Tue, 20 Nov 2018 13:42:35 +0000
Bug 1445943 - Add Enterprise Policy support for macOS to ESR. This includes patches in bug 1445943, bug 1497408, bug 1497948, bug 1498032. r=mstange,felipe,glandium,spohl, a=lizzard
c419540e75dadc4ad89c596e43511c7265ab586b: Bug 1507614 - Identify ESR with MOZ_APP_VERSION_DISPLAY. r=glandium, a=lizzard
Michael Kaply <mozilla@kaply.com> - Thu, 15 Nov 2018 21:32:53 +0000 - rev 450481
Push 242 by ryanvm@gmail.com at Mon, 19 Nov 2018 18:04:04 +0000
Bug 1507614 - Identify ESR with MOZ_APP_VERSION_DISPLAY. r=glandium, a=lizzard Differential Revision: https://phabricator.services.mozilla.com/D12067
4503802587c82e204de340291ce9b403753b82fa: Bug 1445943 - Add Enterprise Policy support for macOS to ESR. This includes patches in bug 1445943, bug 1497408, bug 1497948, bug 1498032. r=mstange,felipe,glandium,spohl, a=lizzard
Stephen A Pohl <spohl.mozilla.bugs@gmail.com> - Tue, 13 Nov 2018 12:33:00 -0500 - rev 450474
Push 241 by ryanvm@gmail.com at Mon, 19 Nov 2018 13:42:46 +0000
Bug 1445943 - Add Enterprise Policy support for macOS to ESR. This includes patches in bug 1445943, bug 1497408, bug 1497948, bug 1498032. r=mstange,felipe,glandium,spohl, a=lizzard
d1c9b0924148c651f61c8305e71d21670876a472: Bug 1475566 - Disable #pragma comments for MinGW Builds. r=glandium, a=lizzard
Tom Ritter <tom@mozilla.com> - Fri, 02 Nov 2018 13:35:51 -0500 - rev 450456
Push 236 by ryanvm@gmail.com at Tue, 13 Nov 2018 00:43:03 +0000
Bug 1475566 - Disable #pragma comments for MinGW Builds. r=glandium, a=lizzard In the MinGW browser build job, we're going to use -fms-extensions, which will tell clang to start processing these comments. Clang cannot process them correctly (it's an upstream bug) but it doesn't need to, because we include the libs we need in moz.build files. So we exclude them for MinGW builds. mingw-clang gets them wrong and mingw-gcc (which doesn't even work anymore on -central) ignored them. In the future, with a llvm fix, we could clean up the moz.build files and re-enable these comments.
2f22204ace0a61ef0071a907f9dadb5131e94879: Bug 1491788 - Use clang 7final to build mingw r=glandium
Sylvestre Ledru <sledru@mozilla.com> - Mon, 17 Sep 2018 13:48:24 +0200 - rev 450391
Push 234 by mozilla@hocat.ca at Sat, 10 Nov 2018 00:08:05 +0000
Bug 1491788 - Use clang 7final to build mingw r=glandium Differential Revision: https://phabricator.services.mozilla.com/D6018
0c1aca3bb1b6ccc165a66c6c438e5e748fb8da8f: Bug 1490564 Add a x86 MinGW-clang toolchain job r=glandium
Tom Ritter <tom@mozilla.com> - Mon, 17 Sep 2018 15:39:14 +0000 - rev 450385
Push 234 by mozilla@hocat.ca at Sat, 10 Nov 2018 00:08:05 +0000
Bug 1490564 Add a x86 MinGW-clang toolchain job r=glandium Differential Revision: https://phabricator.services.mozilla.com/D5720
896a6b159815e5511c4845a4085be2ba8329f91f: Bug 1490567 - Update ffi build to handle x86 MinGW-clang builds. r=glandium, a=lizzard
Tom Ritter <tom@mozilla.com> - Fri, 14 Sep 2018 02:08:17 +0000 - rev 450289
Push 229 by ryanvm@gmail.com at Thu, 08 Nov 2018 22:08:37 +0000
Bug 1490567 - Update ffi build to handle x86 MinGW-clang builds. r=glandium, a=lizzard Differential Revision: https://phabricator.services.mozilla.com/D5643
6546ee839d3002b595765008da323eb2422f0317: Bug 1489744 - Fix a bounds violation crash in the prefs parser. r=glandium, a=RyanVM
Nicholas Nethercote <nnethercote@mozilla.com> - Tue, 11 Sep 2018 09:36:07 +1000 - rev 450118
Push 179 by ryanvm@gmail.com at Wed, 19 Sep 2018 01:11:39 +0000
Bug 1489744 - Fix a bounds violation crash in the prefs parser. r=glandium, a=RyanVM Currently, if a get_char() call returns EOF, the index moves beyond the buffer's bounds and get_char() cannot be called again without triggering a panic. As a result, everywhere that encounters an EOF and then does subsequent parsing ungets the EOF... except there was one place that failed to do that: the match case for CharKind::Slash in get_token(). This meant that a single '/' at the end of the input could trigger a bounds violation (but only if it is the start of a new token). This EOF-unget requirement is subtle and easy to get wrong, so this patch eliminates it. get_char() now can be called repeatedly after an EOF, and will return EOF on each subsequent call. This means that some of the existing unget_char() calls can be removed. Some others are still necessary to get line numbers correct in error messages, but the outcome of mishandled cases is now much less drastic -- an incorrect line number in an error message instead of a panic. The patch also clarifies a couple of related comments.
ff7b658f52501134bab7095ad1a9d5aad7e2f9ad: Bug 1460777 - Taskgraph tasks for retrieving remote content; r=dustin, glandium
Gregory Szorc <gps@mozilla.com> - Thu, 12 Jul 2018 09:55:46 -0600 - rev 450055
Push 159 by mozilla@hocat.ca at Thu, 30 Aug 2018 18:54:58 +0000
Bug 1460777 - Taskgraph tasks for retrieving remote content; r=dustin, glandium Currently, many tasks fetch content from the Internets. A problem with that is fetching from the Internets is unreliable: servers may have outages or be slow; content may disappear or change out from under us. The unreliability of 3rd party services poses a risk to Firefox CI. If services aren't available, we could potentially not run some CI tasks. In the worst case, we might not be able to release Firefox. That would be bad. In fact, as I write this, gmplib.org has been unavailable for ~24 hours and Firefox CI is unable to retrieve the GMP source code. As a result, building GCC toolchains is failing. A solution to this is to make tasks more hermetic by depending on fewer network services (which by definition aren't reliable over time and therefore introduce instability). This commit attempts to mitigate some external service dependencies by introducing the *fetch* task kind. The primary goal of the *fetch* kind is to obtain remote content and re-expose it as a task artifact. By making external content available as a cached task artifact, we allow dependent tasks to consume this content without touching the service originally providing that content, thus eliminating a run-time dependency and making tasks more hermetic and reproducible over time. We introduce a single "fetch-url" "using" flavor to define tasks that fetch single URLs and then re-expose that URL as an artifact. Powering this is a new, minimal "fetch" Docker image that contains a "fetch-content" Python script that does the work for us. We have added tasks to fetch source archives used to build the GCC toolchains. Fetching remote content and re-exposing it as an artifact is not very useful by itself: the value is in having tasks use those artifacts. We introduce a taskgraph transform that allows tasks to define an array of "fetches." Each entry corresponds to the name of a "fetch" task kind. When present, the corresponding "fetch" task is added as a dependency. And the task ID and artifact path from that "fetch" task is added to the MOZ_FETCHES environment variable of the task depending on it. Our "fetch-content" script has a "task-artifacts" sub-command that tasks can execute to perform retrieval of all artifacts listed in MOZ_FETCHES. To prove all of this works, the code for fetching dependencies when building GCC toolchains has been updated to use `fetch-content`. The now-unused legacy code has been deleted. This commit improves the reliability and efficiency of GCC toolchain tasks. Dependencies now all come from task artifacts and should always be available in the common case. In addition, `fetch-content` downloads and extracts files concurrently. This makes it faster than the serial application which we were previously using. There are some things I don't like about this commit. First, a new Docker image and Python script for downloading URLs feels a bit heavyweight. The Docker image is definitely overkill as things stand. I can eventually justify it because I want to implement support for fetching and repackaging VCS repositories and for caching Debian packages. These will require more packages than what I'm comfortable installing on the base Debian image, therefore justifying a dedicated image. The `fetch-content static-url` sub-command could definitely be implemented as a shell script. But Python is readily available and is more pleasant to maintain than shell, so I wrote it in Python. `fetch-content task-artifacts` is more advanced and writing it in Python is more justified, IMO. FWIW, the script is Python 3 only, which conveniently gives us access to `concurrent.futures`, which facilitates concurrent download. `fetch-content` also duplicates functionality found elsewhere. generic-worker's task payload supports a "mounts" feature which facilitates downloading remote content, including from a task artifact. However, this feature doesn't exist on docker-worker. So we have to implement downloading inside the task rather than at the worker level. I concede that if all workers had generic-worker's "mounts" feature and supported concurrent download, `fetch-content` wouldn't need to exist. `fetch-content` also duplicates functionality of `mach artifact toolchain`. I probably could have used `mach artifact toolchain` instead of writing `fetch-content task-artifacts`. However, I didn't want to introduce the requirement of a VCS checkout. `mach artifact toolchain` has its origins in providing a feature to the build system. And "fetching artifacts from tasks" is a more generic feature than that. I think it should be implemented as a generic feature and not something that is "toolchain" specific. I think the best place for a generic "fetch content" feature is in the worker, where content can be defined in the task payload. But as explained above, that feature isn't universally available. The next best place is probably run-task. run-task already performs generic, very-early task preparation steps, such as performing a VCS checkout. I would like to fold `fetch-content` into run-task and make it all driven by environment variables. But run-task is currently Python 2 and achieving concurrency would involve a bit of programming (or adding package dependencies). I may very well port run-task to Python 3 and then fold fetch-content into it. Or maybe we leave `fetch-content` as a standalone script. MozReview-Commit-ID: AGuTcwNcNJR
16ed2ac69014fe6b492aed15758380fb341ad359: Bug 1443471 - Support mingw clang in skia moz.build. r=glandium, a=RyanVM
Jacek Caban <jacek@codeweavers.com> - Mon, 25 Jun 2018 21:22:02 +0200 - rev 449928
Push 116 by ryanvm@gmail.com at Sun, 15 Jul 2018 17:16:16 +0000
Bug 1443471 - Support mingw clang in skia moz.build. r=glandium, a=RyanVM MozReview-Commit-ID: 4H8bkHyczGM
a43554005a5ab97efc589b1a3325ddb4218479f9: Bug 1443471 - Take clang mingw into account in moz.build files. r=glandium, a=RyanVM
Jacek Caban <jacek@codeweavers.com> - Mon, 25 Jun 2018 20:01:39 +0200 - rev 449927
Push 116 by ryanvm@gmail.com at Sun, 15 Jul 2018 17:16:16 +0000
Bug 1443471 - Take clang mingw into account in moz.build files. r=glandium, a=RyanVM MozReview-Commit-ID: 2vKiHjmI9Hn
0aeece86e02dab4b8c193df1bef16018f278dd53: Bug 1443471 - Use correct rust target for mingw clang. r=glandium, a=RyanVM
Jacek Caban <jacek@codeweavers.com> - Mon, 25 Jun 2018 19:57:43 +0200 - rev 449926
Push 116 by ryanvm@gmail.com at Sun, 15 Jul 2018 17:16:16 +0000
Bug 1443471 - Use correct rust target for mingw clang. r=glandium, a=RyanVM MozReview-Commit-ID: G40IanxGWXv
6213468203898d1183c1d30a45f7689ca6368a6a: Bug 1471556 - Support mingw clang in configure scripts. r=glandium, a=RyanVM
Jacek Caban <jacek@codeweavers.com> - Tue, 26 Jun 2018 18:53:42 +0200 - rev 449924
Push 115 by ryanvm@gmail.com at Sun, 15 Jul 2018 17:03:19 +0000
Bug 1471556 - Support mingw clang in configure scripts. r=glandium, a=RyanVM MozReview-Commit-ID: GKLbHvYgXnL
0a420f6c4295c7b7ae27e1aec45db22f326b444e: Bug 1471643 - Use -std=gnu89 for libpng compilation on mingw. r=glandium, a=RyanVM
Jacek Caban <jacek@codeweavers.com> - Wed, 27 Jun 2018 17:03:15 +0200 - rev 449910
Push 114 by ryanvm@gmail.com at Sun, 15 Jul 2018 16:47:34 +0000
Bug 1471643 - Use -std=gnu89 for libpng compilation on mingw. r=glandium, a=RyanVM MozReview-Commit-ID: 3JnNunChnv
b8d266ef27f9801e8b3b3760ce93e4e16c6d8eb7: Bug 1471293 - Support using llvm-objdump in dependentlibs.py. r=glandium, a=RyanVM
Jacek Caban <jacek@codeweavers.com> - Tue, 26 Jun 2018 15:15:19 +0200 - rev 449905
Push 113 by ryanvm@gmail.com at Fri, 13 Jul 2018 21:59:42 +0000
Bug 1471293 - Support using llvm-objdump in dependentlibs.py. r=glandium, a=RyanVM MozReview-Commit-ID: 8b0o06EQh3n
cb6c49908cfe22caf6e2dabafcd2040f6efac73a: Bug 1469676 - Reduce max-run-time for various build tasks; r=glandium
Gregory Szorc <gps@mozilla.com> - Wed, 20 Jun 2018 20:59:01 +0000 - rev 449873
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1469676 - Reduce max-run-time for various build tasks; r=glandium The max-run-time for tasks appears to have been mostly cargo culted. In particular, a value of 36000 (10 hours) is quite absurd: no single task takes that long to execute. This commit reduces the max-run-time of several tasks to more reasonable values. The goal here is to prevent excessively long-running tasks. There is definitely room to further tweak values to further mitigate long-running tasks. But let's bite off the biggest chunk first, since that doesn't require much mental effort. There is a possibility I overshot on some of these tasks. If we get timeouts, we can always increase the timeout again. Differential Revision: https://phabricator.services.mozilla.com/D1716
4c064d7f7f7aa2f8d0273d439104350d82c2368d: Bug 1460777 - Extract GPG keys to standalone files; r=glandium
Gregory Szorc <gps@mozilla.com> - Fri, 11 May 2018 10:38:35 -0700 - rev 449844
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1460777 - Extract GPG keys to standalone files; r=glandium After this change, we consistently import GPG keys from files in the GCC build scripts. MozReview-Commit-ID: BcyvCQoGbMS
bdd2b744c28fa6d58252bec989107041e6494d7d: Bug 1466746 - Install python-zstandard in debian-base; r=glandium
Gregory Szorc <gps@mozilla.com> - Mon, 04 Jun 2018 23:21:19 -0700 - rev 449842
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1466746 - Install python-zstandard in debian-base; r=glandium Let's install python-zstandard for both Python 2 and Python 3 in all our Debian-based images so it is readily available for use. MozReview-Commit-ID: 1L8zDc5MYXA
df304cb358fba6601af10c53da348d9b0bd0c3d4: Bug 1466746 - Debian packages for python-zstandard; r=glandium
Gregory Szorc <gps@mozilla.com> - Mon, 04 Jun 2018 23:10:59 -0700 - rev 449841
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1466746 - Debian packages for python-zstandard; r=glandium python-zstandard's 0.9.1 source distribution contains a debian/ directory. On Squeeze, producing a Debian package is straightforward. On Wheezy, we need to hack up Build-Depends because Wheezy doesn't have a package for the Hypothesis fuzzing library. This package is only used for testing and our package building disables testing, so we don't even need to further hack up the packaging to disable tests. MozReview-Commit-ID: 6raXjdzggCH
4dbf9778f0948e836c7d90120c0ed0851a657b0c: Bug 1466746 - dh-python backport for wheezy; r=glandium
Gregory Szorc <gps@mozilla.com> - Mon, 04 Jun 2018 23:06:01 -0700 - rev 449840
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1466746 - dh-python backport for wheezy; r=glandium dh-python isn't available in Wheezy. Let's backport it so we can build Python packages that use it. Fortunately for us, the package builds without any modifications. The only customization we need is to ensure our custom Python packages are present in order to satisfy Build-Depends. MozReview-Commit-ID: CqZtwvosA6K
5af8c37f769f7333ea664f2f1882da15d97623f8: Bug 1460451 - Add /usr/bin/python3 to Debian images; r=glandium
Gregory Szorc <gps@mozilla.com> - Wed, 09 May 2018 19:54:21 -0700 - rev 449698
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1460451 - Add /usr/bin/python3 to Debian images; r=glandium The python3-minimal package provides /usr/bin/python3 on Debian. This commit installs this package so a `python3` executable is provided. This required backporting the package to wheezy. The final patch is trivial. But I wasted a bit of time figuring out why `mk-build-deps` wasn't working. It would no-op and exit 0 and then the build would complain about missing dependencies! glandium's theory is that the ":any" multiarch support on wheezy isn't complete. Removing ":any" seems to make things "just work." MozReview-Commit-ID: FBicpK4SmkQ
7f0a3e431346a5beb1982f9fc93b8bbf522b717a: Bug 1449629 - Install Python 3.5 in debian-base; r=glandium
Gregory Szorc <gps@mozilla.com> - Mon, 02 Apr 2018 16:58:21 -0700 - rev 449582
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1449629 - Install Python 3.5 in debian-base; r=glandium We want Python 3.5+ to be available everywhere so various processes can start using it. The debian-base Dockerfile is shared by Debian 7 and 9 images. Debian 9 ships with Python 3.5 and after the previous commit, we have a Python 3.5 package for Debian 7. So we simply install the "python3.5" package to get Python on all the Debian images. MozReview-Commit-ID: 9ZmoSxtHWTZ
5d446c0d62089d080bcc0e7e5c1bd4ceb535f045: Bug 1449629 - Install Python 3.5 in Debian 7 base image; r=glandium
Gregory Szorc <gps@mozilla.com> - Mon, 02 Apr 2018 19:27:12 -0700 - rev 449581
Push 108 by mozilla@hocat.ca at Fri, 13 Jul 2018 17:30:31 +0000
Bug 1449629 - Install Python 3.5 in Debian 7 base image; r=glandium Debian 7 ships Python 3.2 by default. That's too old for our upcoming build requirement of Python 3.5. This commit adds a Python 3.5 package for wheezy that backports the Python 3.5 from a much later Debian version. The patch was inspired by the existing patch for Python 2.7. However, it needed additional work. The changes and reasons should all be documented in the changelog file as part of the package diff we apply. I'm a bit disappointed we had to disable PGO. But it was reliably segfaulting during the build. I didn't feel like going down that rabbit hole. MozReview-Commit-ID: ABpHW1KYFQP
562dc783be1a7a2242ef9e860e4447154e88312e: Bug 1460720 - Do not define _aligned_malloc - instead define _aligned_malloc_impl and export _aligned_malloc. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Tue, 15 May 2018 11:10:48 -0500 - rev 449346
Push 44 by ryanvm@gmail.com at Wed, 23 May 2018 02:12:48 +0000
Bug 1460720 - Do not define _aligned_malloc - instead define _aligned_malloc_impl and export _aligned_malloc. r=glandium, a=jcristau MozReview-Commit-ID: 3EwAd81Iz7r
f14e73288315189505508c50698133add2d255e9: Bug 1420350 - Enable jemalloc on MinGW. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Wed, 07 Mar 2018 10:49:28 -0600 - rev 449345
Push 44 by ryanvm@gmail.com at Wed, 23 May 2018 02:12:48 +0000
Bug 1420350 - Enable jemalloc on MinGW. r=glandium, a=jcristau MozReview-Commit-ID: 6YUeFAJocHj
33b018306051cf27cf27d89b3dcff6a1e7d8f6ec: Bug 1448749 - Resolve undefined references to '_imp__mozalloc_abort' in the MinGW build. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Wed, 16 May 2018 22:02:05 -0500 - rev 449343
Push 44 by ryanvm@gmail.com at Wed, 23 May 2018 02:12:48 +0000
Bug 1448749 - Resolve undefined references to '_imp__mozalloc_abort' in the MinGW build. r=glandium, a=jcristau MozReview-Commit-ID: 5enjU5Xp8G9
5962d597aa946c73d7047337882dad4890b19c52: Bug 1443823 - Apply no-keep-inline-dllexport to MinGW x64 also. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Fri, 23 Mar 2018 14:35:30 -0500 - rev 449331
Push 41 by ryanvm@gmail.com at Tue, 22 May 2018 22:53:43 +0000
Bug 1443823 - Apply no-keep-inline-dllexport to MinGW x64 also. r=glandium, a=jcristau MozReview-Commit-ID: 2Nyw738ZHou
b63a4acbf1f84cf76e1e821f40f2149bd8bc7a9f: Bug 1457598 - Add MinGW and GCC scripts to the resources of fxc2 and nsis to ensure they get rebuilt. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Wed, 16 May 2018 12:59:23 -0500 - rev 449324
Push 40 by ryanvm@gmail.com at Tue, 22 May 2018 21:33:12 +0000
Bug 1457598 - Add MinGW and GCC scripts to the resources of fxc2 and nsis to ensure they get rebuilt. r=glandium, a=jcristau
b20aeb0746e7174522fec1f80a623adfb8b507eb: Bug 1440013 - For MinGW build, pass -Wa,-mbig-obj to solve 'too many sections' errors. r=glandium, a=jcristau
Tom Ritter <tom@mozilla.com> - Tue, 06 Mar 2018 16:40:38 -0600 - rev 449313
Push 39 by ryanvm@gmail.com at Tue, 22 May 2018 19:17:13 +0000
Bug 1440013 - For MinGW build, pass -Wa,-mbig-obj to solve 'too many sections' errors. r=glandium, a=jcristau MozReview-Commit-ID: 9ObJnrcpeKe
8e016d7b01bbafb36d5198273d8f4c801782c108: Bug 1422930 - Fix SpiderMonkey includedir installs. r=glandium, a=jcristau
Philip Chimento <philip.chimento@gmail.com> - Mon, 14 May 2018 10:29:00 -0400 - rev 449311
Push 39 by ryanvm@gmail.com at Tue, 22 May 2018 19:17:13 +0000
Bug 1422930 - Fix SpiderMonkey includedir installs. r=glandium, a=jcristau Somehow the header files were being installed directly into $prefix/include, rather than $prefix/include/mozjs-60. Something else changed somewhere that affected this, since this code was the same in older mozjs versions, but this seems the most logical place to fix it.
95ba1f679492ccdaf17e5f62448673c46e61b5c5: Bug 1440461 - Disable titlebar rendering for Linux/Firefox 59. r=glandium, a=lizzard
Martin Stransky <stransky@redhat.com> - Thu, 22 Feb 2018 21:56:58 +0100 - rev 448918
Push 2 by asasaki@mozilla.com at Thu, 26 Apr 2018 19:58:18 +0000
Bug 1440461 - Disable titlebar rendering for Linux/Firefox 59. r=glandium, a=lizzard The titlebar rendering on Linux/Gtk+ is recently enabled at Beta59 but with many bugs fixed at Nightly. Let's disable this feature for Beta / Release 59 and ship it at Firefox 60 where majority of the issues are fixed. MozReview-Commit-ID: FQL7tNhcvUG