134d3abde30cabf888b1e8b9a4dadd94cd872482: Bug 1325351 part 2 - Simplify 'Some' function. r=froydnj
Xidorn Quan <me@upsuper.org> - Fri, 23 Dec 2016 11:32:33 +1100 - rev 454618
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1325351 part 2 - Simplify 'Some' function. r=froydnj MozReview-Commit-ID: AkLVQw9WYwy
a5917e9614e49308f6e9963ee6c38517fef48416: Bug 1325351 part 1 - Remove workaround for VC in Maybe. r=froydnj
Xidorn Quan <me@upsuper.org> - Thu, 29 Dec 2016 10:58:01 +1100 - rev 454617
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1325351 part 1 - Remove workaround for VC in Maybe. r=froydnj MozReview-Commit-ID: Anlrf3D2WtN
aa940ccb1d9f19bcbc8eed23b185a35fe5bb2c4e: Bug 1324998 - Error out when a in-tree mozconfig is included. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 21 Dec 2016 16:58:38 +0900 - rev 454616
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1324998 - Error out when a in-tree mozconfig is included. r=gps Many people have been shooting themselves in the foot for too long by including in-tree mozconfigs. This change adds a guard that makes it an error when this happens on builds not running on automation. Analysis of the in-tree mozconfigs indicate that build/mozconfig.automation is properly included by the in-tree mozconfig that matter, directly or indirectly. The only ones that don't include it are: b2g/config/mozconfigs/common.override b2g/graphene/config/mozconfigs/common.override browser/config/mozconfigs/linux64/source browser/config/mozconfigs/win64/common-win64 build/mozconfig.cache build/mozconfig.clang-cl build/mozconfig.common.override build/mozconfig.rust build/mozconfig.vs-common build/mozconfig.win-common build/unix/mozconfig.gtk build/unix/mozconfig.stdcxx build/win32/mozconfig.vs-latest build/win32/mozconfig.vs2015-win64 build/win64/mozconfig.vs-latest build/win64/mozconfig.vs2015 mobile/android/config/mozconfigs/common.override which are either empty for use in try builds (override files), or would already cause great pain if they were directly included, so there's little chance they would be.
1775ed1787ba133b25ad6611b1cfde9a8fe08680: Bug 1324998 - Set MOZ_AUTOMATION on rooting hazards builds. r=mshal
Mike Hommey <mh+mozilla@glandium.org> - Thu, 22 Dec 2016 15:02:45 +0900 - rev 454615
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1324998 - Set MOZ_AUTOMATION on rooting hazards builds. r=mshal
daea17652fc8d9719ece049101b26047026657a4: Bug 1325217 - Remove Windows Vista from <supportedOS> manifest. r=jimm
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Thu, 22 Dec 2016 07:17:30 +0900 - rev 454614
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1325217 - Remove Windows Vista from <supportedOS> manifest. r=jimm MozReview-Commit-ID: BoZo3XKCgv0
9a78a4e9b5980d2f6b0f00252b1339318af01020: Backed out 4 changesets (bug 1323770) for marionette bustage a=backout
Wes Kocher <wkocher@mozilla.com> - Wed, 28 Dec 2016 14:09:26 -0800 - rev 454613
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Backed out 4 changesets (bug 1323770) for marionette bustage a=backout Backed out changeset bb8ccabdbe27 (bug 1323770) Backed out changeset f1fbf0853e4f (bug 1323770) Backed out changeset d0e5cb3af786 (bug 1323770) Backed out changeset 71e82343afb9 (bug 1323770)
2b12bf8d14cfe2deab64120bbf575edde6e915dd: Backed out changeset 2aef437d23b7 (bug 1309065) for failures in test_css-properties-db.js a=backout
Wes Kocher <wkocher@mozilla.com> - Wed, 28 Dec 2016 13:42:19 -0800 - rev 454612
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Backed out changeset 2aef437d23b7 (bug 1309065) for failures in test_css-properties-db.js a=backout
bb8ccabdbe2746ad256f602a8a849d39c86ae28e: Bug 1323770 - Fix inappropriatelly skipped/disabled tests. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Wed, 21 Dec 2016 17:34:59 +0100 - rev 454611
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1323770 - Fix inappropriatelly skipped/disabled tests. r=maja_zf Commenting out test methods is not the way how we should mark tests as being skipped. The correct skip methods have to be used instead so that the final results also show the correct skip count. MozReview-Commit-ID: LKL4YQCyFko
f1fbf0853e4f78a01102b47b4809c6058fb7723b: Bug 1323770 - Fix skip decorators for unit tests. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Wed, 28 Dec 2016 16:49:44 +0100 - rev 454610
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1323770 - Fix skip decorators for unit tests. r=maja_zf Marionette's skip decorators are currently not conform with the ones from the Python's unittest module, which require a reason as parameter. As such Marionette should behave the same and should also require a reason for more detailed skip messages. This is done by wrapping the actual decorator with another enclosing method. With the changes we also ensure that the wrapper has the same attributes as the wrapped function by using functools.wraps(). This hasn't used so far and makes debugging harder. Further a couple of skip methods and classes were copied from the unittest module, which should be better imported instead to reduce code duplication. MozReview-Commit-ID: 6XT6M6cbCFW
d0e5cb3af786de9ec377a1e58014fb9af7ead9c5: Bug 1323770 - Marionette should not take screenshots for skipped tests. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Wed, 21 Dec 2016 15:19:40 +0100 - rev 454609
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1323770 - Marionette should not take screenshots for skipped tests. r=maja_zf Taking screenshots for skipped tests is useless and should be avoided to reduce the size of the test logs. MozReview-Commit-ID: 9HPH7pSXTj9
71e82343afb96f5c77f2030b21bb47700aa5dd20: Bug 1323770 - Moztest should forward correct test result. r=ahal
Henrik Skupin <mail@hskupin.info> - Wed, 21 Dec 2016 11:19:36 +0100 - rev 454608
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1323770 - Moztest should forward correct test result. r=ahal Registered callback handlers for tests should receive the correct test status when the test has been finished, and not always "Error". This change allows those callbacks to run specific code for individual test results, eg. only do screenshots for failures. MozReview-Commit-ID: FfbCRR0Jvjb
2aef437d23b70db882bfdda054cfb4396e315a6b: Bug 1309065 - Be smarter about filling in the client-side css properties db; r=tromey
gtatum@mozilla.com <gtatum@mozilla.com> - Tue, 11 Oct 2016 20:30:24 +0000 - rev 454607
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1309065 - Be smarter about filling in the client-side css properties db; r=tromey MozReview-Commit-ID: BOYwveTH1Hy
614959839ad77435aa6883b6e2a5424b66b44484: Bug 1325398 - Make the check for duplicate Treeherder symbols, happen during `full` graph not `target` graph stage. r=dustin
Justin Wood <Callek@gmail.com> - Thu, 22 Dec 2016 11:45:10 -0500 - rev 454606
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1325398 - Make the check for duplicate Treeherder symbols, happen during `full` graph not `target` graph stage. r=dustin MozReview-Commit-ID: GfwAgERKdsL
7cfa5f7c0ec2c6da408e4a2fb034af19989aee93: Bug 1318796 - Open the appropriate tool when clicking on a location in the new console; r=jdescottes
Nicolas Chevobbe <chevobbe.nicolas@gmail.com> - Thu, 01 Dec 2016 08:29:43 +0100 - rev 454605
Push 39990 by bmo:jaws@mozilla.com at Thu, 29 Dec 2016 20:26:23 +0000
Bug 1318796 - Open the appropriate tool when clicking on a location in the new console; r=jdescottes We were always opening the debugger when clicking on the location link, which could be wrong since we can have CSS warnings, or logs coming from Scratchpad. So we add the function to open in StyleEditor and Scratchpad, and copy some mochitests that where testing the interaction with those links. MozReview-Commit-ID: 73mQNfy199m
85b7e50223647d2c0b4b6861a36e433db59641a0: Bug 1245921 - Update tests for toolbox toolbar; r?miker draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 18 Nov 2016 15:05:02 -0600 - rev 454604
Push 39989 by bmo:gtatum@mozilla.com at Thu, 29 Dec 2016 20:23:04 +0000
Bug 1245921 - Update tests for toolbox toolbar; r?miker MozReview-Commit-ID: EnFqSy2day4
9319aaf8c7c1c7983ba5f635ef8855b718f9a56d: Bug 1245921 - Turn toolbox toolbar into a React component r?miker draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 18 Nov 2016 15:02:21 -0600 - rev 454603
Push 39989 by bmo:gtatum@mozilla.com at Thu, 29 Dec 2016 20:23:04 +0000
Bug 1245921 - Turn toolbox toolbar into a React component r?miker I separated out the tests from this commit to make the review easier, but I will squash the two whenever I land them. I apologize in advance for the size of this patch. I didn't see any way to do it in small incremental work. MozReview-Commit-ID: 4UZbcfw2YI9
bb3cd5fba24f3034b3e9e3909c11c14b52247b6d: Bug 1245921 - Monkey patch ReactDOM event system for XUL; r?miker draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 23 Dec 2016 15:57:03 -0600 - rev 454602
Push 39989 by bmo:gtatum@mozilla.com at Thu, 29 Dec 2016 20:23:04 +0000
Bug 1245921 - Monkey patch ReactDOM event system for XUL; r?miker XUL iframes inside of a privileged XUL document propagate events between the documents. This breaks React's event model, as React captures all events at the document level. In the XUL document containing a XUL iframe, these events end up being dispatched twice. This fix tricks react into thinking the toolbox.xul document is the only root document, thus fixing the event system. MozReview-Commit-ID: B3XF3L6rax1
e786066e3f9e6c8057a7f6f389b95efa641c8133: Bug 1245921 - Update tests for toolbox toolbar; r?miker draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 18 Nov 2016 15:05:02 -0600 - rev 454601
Push 39988 by bmo:gtatum@mozilla.com at Thu, 29 Dec 2016 20:18:09 +0000
Bug 1245921 - Update tests for toolbox toolbar; r?miker MozReview-Commit-ID: EnFqSy2day4
ff4212c3ced7534a249b8b23681aa617dc295bea: Bug 1245921 - Turn toolbox toolbar into a React component r?miker draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 18 Nov 2016 15:02:21 -0600 - rev 454600
Push 39988 by bmo:gtatum@mozilla.com at Thu, 29 Dec 2016 20:18:09 +0000
Bug 1245921 - Turn toolbox toolbar into a React component r?miker I separated out the tests from this commit to make the review easier, but I will squash the two whenever I land them. I apologize in advance for the size of this patch. I didn't see any way to do it in small incremental work. MozReview-Commit-ID: 4UZbcfw2YI9
ecf8c09cdb8a10eae2f809c3670fc624bda59084: Bug 1245921 - Monkey patch ReactDOM event system for XUL; r?miker draft
Greg Tatum <tatum.creative@gmail.com> - Fri, 23 Dec 2016 15:57:03 -0600 - rev 454599
Push 39988 by bmo:gtatum@mozilla.com at Thu, 29 Dec 2016 20:18:09 +0000
Bug 1245921 - Monkey patch ReactDOM event system for XUL; r?miker XUL iframes inside of a privileged XUL document propagate events between the documents. This breaks React's event model, as React captures all events at the document level. In the XUL document containing a XUL iframe, these events end up being dispatched twice. This fix tricks react into thinking the toolbox.xul document is the only root document, thus fixing the event system. MozReview-Commit-ID: B3XF3L6rax1
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip