66314092d86f2a1ca7275864d16d6cc6c181762d: Bug 1383880: use a vcs-compatible reader in decision tasks; r?gps draft
Dustin J. Mitchell <dustin@mozilla.com> - Thu, 07 Sep 2017 18:28:22 +0000 - rev 668263
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: use a vcs-compatible reader in decision tasks; r?gps This continues to use a file-based reader when run locally. MozReview-Commit-ID: CJuYKDj2E3n
46e4665f197b989d0de58d8929fbf8d9584bcced: Bug 1383880: add only-if-dependencies-run optimization for follow-ons; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Fri, 25 Aug 2017 21:18:13 +0000 - rev 668262
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: add only-if-dependencies-run optimization for follow-ons; r=ahal MozReview-Commit-ID: JuhwyQIx3Mh
1e0db6a633eccb8ea3edd78cb03b4191cc08c4aa: Bug 1383880: annotate source files with what they SCHEDULE; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Fri, 25 Aug 2017 19:31:54 +0000 - rev 668261
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: annotate source files with what they SCHEDULE; r=ahal MozReview-Commit-ID: CR70dSg5R79
0a61ef73d92b406b29139002618a7cf6c3aa5111: Bug 1383880: Annotate builds and tests with SCHEDULES-related optimizations; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Fri, 25 Aug 2017 19:15:12 +0000 - rev 668260
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: Annotate builds and tests with SCHEDULES-related optimizations; r=ahal This means that a push to try affecting only Android will only run android builds and tests, for example. MozReview-Commit-ID: HVUvIg0EUZn
c5b9cae1789623a120b261e417d908ce2fb5437f: Bug 1383880: add support for optimizing tasks based on SCHEDULES; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Wed, 23 Aug 2017 16:21:06 +0000 - rev 668259
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: add support for optimizing tasks based on SCHEDULES; r=ahal This adds some new optimization strategies. For tests, we use Either(SETA, SkipUnlessSchedules), thereby giving both mechanisms a chance to skip tasks. On try, SETA is omitted. MozReview-Commit-ID: GL4tlwyeBa6
ab4fbe77b8f0803e1dcd25d3d57e927276c15b64: Bug 1383880: add support for SCHEDULES in moz.build; r=gps draft
Dustin J. Mitchell <dustin@mozilla.com> - Mon, 31 Jul 2017 20:44:56 +0000 - rev 668258
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: add support for SCHEDULES in moz.build; r=gps MozReview-Commit-ID: 2pfLr0VTy2J
84ca2e70351f14291274cd1faa74481362370c0d: Bug 1383880: parse try config during the decision task; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Mon, 21 Aug 2017 23:14:14 +0000 - rev 668257
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: parse try config during the decision task; r=ahal This sets the try_mode property, and parses the try message (if given), early in the decision task and puts the results into the parameters. The proximate need is to set optimze_target_tasks for some try modes and not others. This also replaces the existing logic for parsing messages for certain kinds, and makes the distinction between the different try modes a little clearer. MozReview-Commit-ID: AXJEGLh6pEV
820aa768e9e9048d4b8e04ce70af71001ade454e: Bug 1383880: optimize in three phases; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Sun, 20 Aug 2017 20:00:17 +0000 - rev 668256
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: optimize in three phases; r=ahal In preparation for much more thorough optimization of task-graphs, this makes a few changes: * optimization is split into thre phases, with task removal in one phase (following dependency links) and task replacement in the next (in the reverse order). * optimization uses class instances instead of functions for optimizations; this allows different functions for different phases, and also leaves open the possibility of composing optimizations. * the replacement phase can also support removal; this is when utility tasks like symbol uploads can be optimized away iff their parent task is optimized. MozReview-Commit-ID: C5QznNpwqXn
8b227cc78b03f1836a7649365fbb6ae5363f0cc5: Bug 1383880: add Graph.visit_preorder; r=ahal draft
Dustin J. Mitchell <dustin@mozilla.com> - Sun, 20 Aug 2017 16:29:12 +0000 - rev 668255
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: add Graph.visit_preorder; r=ahal MozReview-Commit-ID: BWGqLUuWlN9
85327e0d04775d813abfbecf9f8065e191a56ee9: Bug 1383880: allow only one optimization per task; r=ahal,r=glandium draft
Dustin J. Mitchell <dustin@mozilla.com> - Tue, 01 Aug 2017 20:02:59 +0000 - rev 668254
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1383880: allow only one optimization per task; r=ahal,r=glandium It is not at *all* clear how multiple optimizations for a single task should interact. No simple logical operation is right in all cases, and in fact in most imaginable cases the desired behavior turns out to be independent of all but one of the optimizations. For example, given both `seta` and `skip-unless-files-changed` optimizations, if SETA says to skip a test, it is low value and should be skipped regardless of what files have changed. But if SETA says to run a test, then it has likely been skipped in previous pushes, so it should be run regardless of what has changed in this push. This also adds a bit more output about optimization, that may be useful for anyone wondering why a particular job didn't run. MozReview-Commit-ID: 3OsvRnWjai4
7612ac815868741592443f7161b33b37af87ee10: Bug 1401183: raise KeyError from list_artifacts when none is found; r=glandium draft
Dustin J. Mitchell <dustin@mozilla.com> - Thu, 14 Sep 2017 23:30:58 +0000 - rev 668253
Push 80997 by dmitchell@mozilla.com at Thu, 21 Sep 2017 12:46:24 +0000
Bug 1401183: raise KeyError from list_artifacts when none is found; r=glandium MozReview-Commit-ID: TqON8joEd6
1f26159171eda569e884466ddb6eba73e0cd4c0b: Bug 1401937 - Fix the command to generate webext-langpacks. r=pike draft
Zibi Braniecki <zbraniecki@mozilla.com> - Thu, 21 Sep 2017 14:38:56 +0200 - rev 668252
Push 80996 by bmo:gandalf@aviary.pl at Thu, 21 Sep 2017 12:39:20 +0000
Bug 1401937 - Fix the command to generate webext-langpacks. r=pike MozReview-Commit-ID: 5XXJBqP5ZF9
6cf80bbeb2f05561ac0a83cd7942a47b9382e658: Bug 1395240 - Implement stackTest function for JS stack OOM testing. r?jandem draft
Christian Holler <choller@mozilla.com> - Wed, 20 Sep 2017 14:19:21 +0200 - rev 668251
Push 80995 by choller@mozilla.com at Thu, 21 Sep 2017 12:27:35 +0000
Bug 1395240 - Implement stackTest function for JS stack OOM testing. r?jandem MozReview-Commit-ID: LRFb0adTFR8
18c1e4613dd2df098f9f6a19470342a86d1096f9: Bug 335545 - Count FD instead of looking for clipboardcache in test_bug1123480.xul r?mstange draft
Rob Wu <rob@robwu.nl> - Thu, 21 Sep 2017 14:17:27 +0200 - rev 668250
Push 80994 by bmo:rob@robwu.nl at Thu, 21 Sep 2017 12:21:29 +0000
Bug 335545 - Count FD instead of looking for clipboardcache in test_bug1123480.xul r?mstange - Count open file descriptors instead of testing the existence of a file (because the clipboard is now only reachable through file descriptors, and not through a file path). - Use a fixed string instead of a random string. The previous way of generating a string was non-deterministic, and there was a very small chance that the generated string was not large enough to trigger the cache-to-disk-mode. MozReview-Commit-ID: KOkYOm280Oh
71cd18c4a8b28fbe68b214ddf44082c0c9cdafcc: Bug 335545 - Store clipboard data in memory XOR file draft
Rob Wu <rob@robwu.nl> - Sun, 03 Sep 2017 03:21:45 +0200 - rev 668249
Push 80994 by bmo:rob@robwu.nl at Thu, 21 Sep 2017 12:21:29 +0000
Bug 335545 - Store clipboard data in memory XOR file Ensure that only DataStruct::mData + mDataLen, XOR DataStruct::mCacheFD is used. (Previously it was possible that all of these members were populated, which is a waste of memory.) The effect of this change is visible when SetTransferData is called multiple times with the same flavor, but with one below the threshold for storing in-memory, and the other above (=store in a file). MozReview-Commit-ID: 4UlkKAYsjf
0c1030313a478f2234209ce076d4cf00e0979d0e: Bug 335545 - Use nsAnonymousTemporaryFile for clipboard cache draft
Rob Wu <rob@robwu.nl> - Sun, 03 Sep 2017 02:29:10 +0200 - rev 668248
Push 80994 by bmo:rob@robwu.nl at Thu, 21 Sep 2017 12:21:29 +0000
Bug 335545 - Use nsAnonymousTemporaryFile for clipboard cache The cache file is never directly exposed to consumers of DataStruct, so it does not make sense to keep the clipboardcache file around forever. The only change in this commit is to switch from using a filename to using a file descriptor. In the destructor, the FD is explicitly closed (which releases the file data). nsAnonymousTemporaryFile takes care of removing the file when the destructor is not called (e.g. crashes). Previously, the clipboard cache was stored in a file called: TmpD/clipboardcache-N As of this commit, the clipboard cache is stored at: TmpD/mozilla-temp-randomN (macOS and Linux) TmpD/mozilla-temp-files/mozilla-temp-randomN (Windows) (see xpcom/io/nsAnonymousTemporaryFile.{h,cpp} for more details) To verify that these files are really gone: 1. Create a document with 500k+ characters, open it in Firefox. 2. Copy its content - this will trigger the clipboard cache. 3. Look for the open file descriptor of the deleted file: ( macOS and Linux: ) lsof +L1 | grep mozilla-temp 4. Copy anything (under the 500k threshold), or quit/kill Firefox. 5. Repeat step 3 and observe that the number of file descriptors has decreased. MozReview-Commit-ID: 85GlKQrNUl5
9dc0e920033c8abbb4913e5f2eea79e92b2c3063: Bug 1400846 - Fix ordering of bookmarks with Async Transactions when dropping into different folders. r?mak draft
Mark Banner <standard8@mozilla.com> - Tue, 19 Sep 2017 06:54:16 +0100 - rev 668247
Push 80993 by bmo:standard8@mozilla.com at Thu, 21 Sep 2017 12:20:48 +0000
Bug 1400846 - Fix ordering of bookmarks with Async Transactions when dropping into different folders. r?mak MozReview-Commit-ID: GjnehR5PumZ
4da76d1821734932a717c13df4e1e42f9d9b296e: Bug 1399777 Fprinter directing output to Windows debug console when it outputs to stderr. r=Yoric draft
sourav3 <sourav.mukherjee619@gmail.com> - Thu, 21 Sep 2017 17:06:51 +0800 - rev 668246
Push 80992 by bmo:sourav.mukherjee619@gmail.com at Thu, 21 Sep 2017 12:11:44 +0000
Bug 1399777 Fprinter directing output to Windows debug console when it outputs to stderr. r=Yoric MozReview-Commit-ID: 81ubXofHIlG *** Using PodCopy instead of std::copy and fixing spaces
136f970f019a88d820151dd2bd9372cba1e5953d: Bug 1401930 - Correct query selectors in DownloadsSubview code. r?Paolo draft
Mike de Boer <mdeboer@mozilla.com> - Thu, 21 Sep 2017 14:01:37 +0200 - rev 668245
Push 80991 by mdeboer@mozilla.com at Thu, 21 Sep 2017 12:07:18 +0000
Bug 1401930 - Correct query selectors in DownloadsSubview code. r?Paolo MozReview-Commit-ID: FDl7k7QkMv2
df579bfbe9f666eaf6bc8a0873210b98a294db43: Bug 1398106 - Check the disabled state for each menuitem in the context menu for a Download in the Library subview. r?Paolo draft
Mike de Boer <mdeboer@mozilla.com> - Thu, 21 Sep 2017 13:55:04 +0200 - rev 668244
Push 80991 by mdeboer@mozilla.com at Thu, 21 Sep 2017 12:07:18 +0000
Bug 1398106 - Check the disabled state for each menuitem in the context menu for a Download in the Library subview. r?Paolo The 'cmd_delete' command was clashing with another controller which keeps disabling the menuitem, so it's been renamed to 'downloadsCmd_delete' instead. MozReview-Commit-ID: IiWEVMt0dfW
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip