caddaa0955f6b53b898a1a3d4df93cfe87d515f3: Bug 1003417 - Add ability to run subsuites to |mach python-test|, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Thu, 17 Nov 2016 16:30:33 -0500 - rev 470490
Push 44047 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:29:59 +0000
Bug 1003417 - Add ability to run subsuites to |mach python-test|, r?ted This adds the ability to use manifestparser subsuites to |mach python-test|. Subsuites are based on the premise of a "default" set that gets run when no subsuites are explicitly specified. When a test is labelled with a subsuite, that test is removed from the default set and will only run if that subsuite is explicitly specified. This will allow us to chunk python unittests out of 'make check' piecemeal. The default set will run in 'make check', and individual tasks (e.g mozbase), will specify a subsuite explicitly. The |mach python-test| implementation is slightly different. By default, subsuites are not considered if developers do not pass in --subsuite. This means running |mach python-test| without arguments will still run the full set of tests, and similarly, passing in test paths will *just work*. If for some reason a developer needs to actually run the default set, a special "default" subsuite has been create, so they can use |mach python-test --subsuite default|. This default subsuite is also what 'make check' will explicitly invoke. MozReview-Commit-ID: FaHb4nvuoK9
bcb208dc1b8ebb68e9c1faf72665c56678e0137c: Bug 1003417 - Include testing/mozbase/moz.build from root moz.build file, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 01 Feb 2017 09:56:33 -0500 - rev 470489
Push 44047 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:29:59 +0000
Bug 1003417 - Include testing/mozbase/moz.build from root moz.build file, r?ted By including the mozbase's moz.build directly in the root moz.build, we are making sure that mozbase unittests will be found even if there is no build/objdir. This will be useful when running mozbase tests in their own taskcluster task. MozReview-Commit-ID: DqqY09I3JBC
94cbebb6f531faa6c29ce9a3f66a040551b9617f: Bug 1329355 - Remove MOZ_PKG_PRETTYNAMES; r?ted draft
Mike Shal <mshal@mozilla.com> - Tue, 10 Jan 2017 11:12:10 -0500 - rev 470488
Push 44046 by bmo:mshal@mozilla.com at Fri, 03 Feb 2017 20:27:26 +0000
Bug 1329355 - Remove MOZ_PKG_PRETTYNAMES; r?ted This is no longer relevant now that we use release promotion instead of a separate release build with MOZ_PKG_PRETTYNAMES=1. MozReview-Commit-ID: 11mgGJ7IDaK
62ba248f716dfd3139d6467133804c5d13a1eddb: Bug 1329355 - Remove MOZ_AUTOMATION_PRETTY*; r?ted draft
Mike Shal <mshal@mozilla.com> - Tue, 10 Jan 2017 11:07:13 -0500 - rev 470487
Push 44046 by bmo:mshal@mozilla.com at Fri, 03 Feb 2017 20:27:26 +0000
Bug 1329355 - Remove MOZ_AUTOMATION_PRETTY*; r?ted These automation steps are no longer relevant, since the last use of MOZ_AUTOMATION_PRETTY was removed along with non-unified builds in bug 1121000. MozReview-Commit-ID: 11VDu8pIs1p
21104950a6b7fd2be13e2d256929b3f36eee1fb0: Bug 1336554 - Add support to e10s-multi for simplified browser tab. r?mconley draft
Matheus Longaray <mlongaray@hp.com> - Fri, 03 Feb 2017 21:21:01 +0100 - rev 470486
Push 44045 by bmo:mlongaray@hp.com at Fri, 03 Feb 2017 20:24:56 +0000
Bug 1336554 - Add support to e10s-multi for simplified browser tab. r?mconley This patch adds support to e10s-multi when creating tab for simplified browser. MozReview-Commit-ID: KHXePRVxrGl
459fc4e6d94c5af6b3fd3388f764f7b107378a6f: Bug 1003417 - Add task for running mozbase python tests on linux, r?dustin draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Fri, 02 Dec 2016 17:21:54 -0500 - rev 470485
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1003417 - Add task for running mozbase python tests on linux, r?dustin This also adds a new 'py' group which should help make it obvious which tasks are python unittests. The tg and MH tasks won't show up in this new py group right away due to a caching bug in the treeherder database, but eventually they should move over. MozReview-Commit-ID: JwL1NAR4bnY
e71be5c6f2cdb1a75a3f30d79a5295c0af5157ce: Bug 1003417 - Use 'ip addr show' instead of 'ifconfig' for moznetwork tests, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Fri, 06 Jan 2017 11:19:19 -0500 - rev 470484
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1003417 - Use 'ip addr show' instead of 'ifconfig' for moznetwork tests, r?jmaher The taskcluster docker image for source-check tasks does not have 'ifconfig' installed. We could add this package, but ifconfig is more or less deprecated in favour of 'ip addr show'. Although the formats of both commands are different, because the test pulls ip addresses out of the output with regexes, the only change that is needed to make sure the tests still pass is to change the command. MozReview-Commit-ID: 758Qb6KSHzS
e33d1fe9a33f81f80f0b2ec5250c9da361eec7a8: Bug 1003417 - Add a 'mozbase' subsuite to python unittests on linux, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 16 Nov 2016 16:43:42 -0500 - rev 470483
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1003417 - Add a 'mozbase' subsuite to python unittests on linux, r?jmaher The subsuite is added conditionally because we only have the capability of running source-check tasks on linux at the moment. Once taskcluster support for windows and mac has matured a bit and the taskcluster configs support source-check there, we should apply the subuite unconditionally. MozReview-Commit-ID: Kk9Irz3fn14
6fde1fe4b46c5c9c3e30886705fdd50b75dc3ead: Bug 1003417 - Add ability to run subsuites to |mach python-test|, r?mshal draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Thu, 17 Nov 2016 16:30:33 -0500 - rev 470482
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1003417 - Add ability to run subsuites to |mach python-test|, r?mshal This adds the ability to use manifestparser subsuites to |mach python-test|. Subsuites are based on the premise of a "default" set that gets run when no subsuites are explicitly specified. When a test is labelled with a subsuite, that test is removed from the default set and will only run if that subsuite is explicitly specified. This will allow us to chunk python unittests out of 'make check' piecemeal. The default set will run in 'make check', and individual tasks (e.g mozbase), will specify a subsuite explicitly. The |mach python-test| implementation is slightly different. By default, subsuites are not considered if developers do not pass in --subsuite. This means running |mach python-test| without arguments will still run the full set of tests, and similarly, passing in test paths will *just work*. If for some reason a developer needs to actually run the default set, a special "default" subsuite has been create, so they can use |mach python-test --subsuite default|. This default subsuite is also what 'make check' will explicitly invoke. MozReview-Commit-ID: FaHb4nvuoK9
eb4d5a3b38582ef8020b52ced8961dd3eb9a7af9: Bug 1003417 - Include testing/mozbase/moz.build from root moz.build file, r?mshal draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 01 Feb 2017 09:56:33 -0500 - rev 470481
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1003417 - Include testing/mozbase/moz.build from root moz.build file, r?mshal By including the mozbase's moz.build directly in the root moz.build, we are making sure that mozbase unittests will be found even if there is no build/objdir. This will be useful when running mozbase tests in their own taskcluster task. MozReview-Commit-ID: DqqY09I3JBC
58b0e5bf67c10ccacfe4d5014f80c0fd18b6a936: Bug 1320194 - Generate all-tests.pkl and related files when resolving tests draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 01 Feb 2017 09:56:09 -0500 - rev 470480
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1320194 - Generate all-tests.pkl and related files when resolving tests This replaces the 'run-tests-deps' make target with a python function that will directly read moz.build files, emit them with TestManifestEmitter, then consume them with TestManifestBackend. Because the TestResolver is the only place that actually reads the test metadata files, we can remove this logic from the CommonBackend as well. MozReview-Commit-ID: DXgMoeH5dKf MozReview-Commit-ID: HstZ57qkqf2
19c0aaae6a71e51f275350bb27e092c7b7b58bb2: Bug 1320194 - Add ability to specify custom emitter function in TreeMetadataEmitter draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Fri, 27 Jan 2017 11:54:09 -0500 - rev 470479
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1320194 - Add ability to specify custom emitter function in TreeMetadataEmitter Currently, the only way to emit objects after reading moz.build, is to emit everything. Though, sometimes it may be desirable to only emit certain types of objects. This adds a new argument that allows consumers to specify a custom emitter function. This gives them the flexibility to do whatever they want. This will be used when resolving tests, so only TestManifest objects are emitted. MozReview-Commit-ID: DPGgNmn2JvE
ccc1d156a5fc773d8456a40848d50f5a4151eee1: Bug 1320194 - Fix bug preventing more than two backends in a HybridBackend draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Fri, 27 Jan 2017 16:31:15 -0500 - rev 470478
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1320194 - Fix bug preventing more than two backends in a HybridBackend This is a drive by fix that is not relevant to the rest of the commit series. MozReview-Commit-ID: Bwrb74o3Qh8
2d277005c3cff39b6f085dfd13ebafd340febc4b: Bug 1320194 - Refactor test metadata related backend code into a partial TestManifestBackend draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Fri, 27 Jan 2017 11:47:34 -0500 - rev 470477
Push 44044 by ahalberstadt@mozilla.com at Fri, 03 Feb 2017 20:22:05 +0000
Bug 1320194 - Refactor test metadata related backend code into a partial TestManifestBackend Currently the CommonBackend is responsible for processing TestManifest objects and using them to generate the test metadata files (e.g all-tests.pkl et al). This patch pulls that logic out into a partial backend specifically for test manifests. This patch is solely a refactoring and shouldn't change any build behaviour. CommonBackend has a TestManifestBackend instance and calls consume_object directly on it. However, this is just a temporary measure to avoid checking in a broken commit. This commit also adds a test for the 'test-defaults.pkl' file which was previously missing. MozReview-Commit-ID: HOr2QVT8CJ1
9500d978c64a25bed3ce6536664580531a9679a2: Bug 1336525 - Install test support binary in uriloader/exthandler/tests with moz.build, not Makefile.in draft
Chris Manchester <cmanchester@mozilla.com> - Fri, 03 Feb 2017 12:18:16 -0800 - rev 470476
Push 44043 by bmo:cmanchester@mozilla.com at Fri, 03 Feb 2017 20:18:44 +0000
Bug 1336525 - Install test support binary in uriloader/exthandler/tests with moz.build, not Makefile.in MozReview-Commit-ID: CLk2YdGJG6a
1d5a0cd395cab58187fd84d59a9264ac24180a50: Bug 1336530 - Re-enable Android tests that were disabled in bug 1298218 and disable the assertion. r?tnikkel draft
Markus Stange <mstange@themasta.com> - Fri, 03 Feb 2017 14:55:51 -0500 - rev 470475
Push 44042 by bmo:mstange@themasta.com at Fri, 03 Feb 2017 19:56:27 +0000
Bug 1336530 - Re-enable Android tests that were disabled in bug 1298218 and disable the assertion. r?tnikkel MozReview-Commit-ID: L7PnRvUkw5O
364e26c1f0a48f612818e253e35587d411832194: Bug 1336519 - Don't try to detect scrolled clips using AGRs in non-APZ mode. r?mattwoodrow draft
Markus Stange <mstange@themasta.com> - Fri, 03 Feb 2017 13:41:37 -0500 - rev 470474
Push 44042 by bmo:mstange@themasta.com at Fri, 03 Feb 2017 19:56:27 +0000
Bug 1336519 - Don't try to detect scrolled clips using AGRs in non-APZ mode. r?mattwoodrow Before bug 1298218, in this if branch with APZ enabled, itemClip was always the display port clip for fixed backgrounds, even for fixed backgrounds on the canvas frame. But after bug 1298218 we no longer clip canvas fixed backgrounds to the display port, so itemClip is now the viewport clip. And that clip is definitely not a scrolled clip, so we must not merge layers around it. The better solution for this would be to remove this if branch completely and fix up the scrolled clip layerization detection for the non-APZ case to also use ASRs. That's tracked by bug 1336516. MozReview-Commit-ID: 2F7hPrldUlq
b7f6a60987de1c824bf3520eaf3d73d18737342e: Bug 1333014 - Support intercepted clicks and align with spec; r?maja_zf,whimboo draft
Andreas Tolfsen <ato@mozilla.com> - Fri, 03 Feb 2017 19:52:34 +0000 - rev 470473
Push 44041 by bmo:ato@mozilla.com at Fri, 03 Feb 2017 19:55:26 +0000
Bug 1333014 - Support intercepted clicks and align with spec; r?maja_zf,whimboo The WebDriver specification changed recently to introduce a new 'element click intercepted' error that is returned if the high-level Element Click command attempts an element that is obscured by another (the other element's z-index, or order in the paint tree, is higher). This patch introduces the notion of 'container elements', which is an element's context. For example, an <option> element's container element or context is the nearest ancestral <select> or <datalist> element. It also makes a distinction between an element being pointer-interactable and merely being in-view. This is important since an element may be in view but not pointer-interactable (i.e. clicking its centre coordinates might be intercepted), and we do not want to wait for an element to become pointer-interactable after scrolling it into view if it is indeed obscured. MozReview-Commit-ID: 8dqGZP6UyOo
483adad2dfedfc4af2aaac6f9f0828596c4a4923: Bug 1333014 - Introduce new exceptions to Python client; r?whimboo draft
Andreas Tolfsen <ato@mozilla.com> - Fri, 03 Feb 2017 19:40:56 +0000 - rev 470472
Push 44041 by bmo:ato@mozilla.com at Fri, 03 Feb 2017 19:55:26 +0000
Bug 1333014 - Introduce new exceptions to Python client; r?whimboo This adds the new errors ElementNotInteractableException and ElementClickInterceptedException to the Marionette Python client. It marks the ElementNotVisibleException as a deprecated, but does not remove it for to backwards compatibility concerns with the Firefox upgrade tests. MozReview-Commit-ID: GPSwMo0fHnk
dc2e1a7165db58c24eed4b8d84930dd4fc9d87b3: Bug 1333014 - Use static lookup of error status; r?whimboo draft
Andreas Tolfsen <ato@mozilla.com> - Fri, 03 Feb 2017 19:31:12 +0000 - rev 470471
Push 44041 by bmo:ato@mozilla.com at Fri, 03 Feb 2017 19:55:26 +0000
Bug 1333014 - Use static lookup of error status; r?whimboo We previously constructed each error instance on loading the testing/marionette/error.js module. We can avoid this overhead by using a static lookup table. MozReview-Commit-ID: 6S7XFvxPZpI
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip