searching for reviewer(bc)
c7147a64ff7b258dc710be70cf238092270a7558: Bug 1573432 - make adb.py python 3 compatible r=bc
Tarek Ziadé <tarek@mozilla.com> - Mon, 19 Aug 2019 14:36:17 +0000 - rev 488727
Push 36454 by opoprus@mozilla.com at Mon, 19 Aug 2019 21:54:53 +0000
Bug 1573432 - make adb.py python 3 compatible r=bc These changes will fix the API that read values out of ADB commands for Python 3. Differential Revision: https://phabricator.services.mozilla.com/D41921
8bd696e50a12db4f6be4ded519ef4f97ed6fed60: Bug 1568861 - Run android-hw mochitest-media against geckoview; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 08 Aug 2019 13:54:07 +0000 - rev 486977
Push 36411 by rmaries@mozilla.com at Fri, 09 Aug 2019 03:49:20 +0000
Bug 1568861 - Run android-hw mochitest-media against geckoview; r=bc Differential Revision: https://phabricator.services.mozilla.com/D41205
38a106b2bf3d3b913fe2737099573b2ab46ed1a6: Bug 1569982 - Respect verify annotations when running tests in mach with --verify; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 06 Aug 2019 22:13:50 +0000 - rev 486616
Push 36400 by aciure@mozilla.com at Wed, 07 Aug 2019 04:33:53 +0000
Bug 1569982 - Respect verify annotations when running tests in mach with --verify; r=bc Test manifest annotations like "skip-if = verify" are normally handled in mozharness: When a TV task finds a modified test that needs verification, but that test is skipped in verify mode, mozharness discards the test from the list of tests to be run. When running tests locally (mach mochitest, etc), these annotations should also be respected, and are currently handled in wpt and reftest harnesses, but not in mochitest or xpcshell -- rectified by this patch. mochitest and xpcshell had neglected to set mozinfo["verify"] when running in verify mode -- easily corrected. It should be noted that when running tests locally and a single test is requested, most test harnesses run the requested test even if it is skip-annotated. Thus, "mach test <test> --verify" will continue to run tests annotated "skip-if = verify" and this patch only changes the mochitest/xpcshell behavior of verify-skipped tests when run with "mach test <directory> --verify" -- a long-running test mode with complex logging never used in continuous integration. Differential Revision: https://phabricator.services.mozilla.com/D40486
4afd3ec36843ae75ee9b09e524a7aa7846045c96: Bug 1569982 - Respect verify annotations when running tests in mach with --verify; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 05 Aug 2019 18:24:52 +0000 - rev 486420
Push 36394 by dluca@mozilla.com at Tue, 06 Aug 2019 09:35:30 +0000
Bug 1569982 - Respect verify annotations when running tests in mach with --verify; r=bc Test manifest annotations like "skip-if = verify" are normally handled in mozharness: When a TV task finds a modified test that needs verification, but that test is skipped in verify mode, mozharness discards the test from the list of tests to be run. When running tests locally (mach mochitest, etc), these annotations should also be respected, and are currently handled in wpt and reftest harnesses, but not in mochitest or xpcshell -- rectified by this patch. mochitest and xpcshell had neglected to set mozinfo["verify"] when running in verify mode -- easily corrected. It should be noted that when running tests locally and a single test is requested, most test harnesses run the requested test even if it is skip-annotated. Thus, "mach test <test> --verify" will continue to run tests annotated "skip-if = verify" and this patch only changes the mochitest/xpcshell behavior of verify-skipped tests when run with "mach test <directory> --verify" -- a long-running test mode with complex logging never used in continuous integration. Differential Revision: https://phabricator.services.mozilla.com/D40486
0fa12d2ad2e5e6a49a12541301be76df0dab41f9: Bug 1570051 - Minor updates to android mach commands; r=bc
Geoff Brown <gbrown@mozilla.com> - Sat, 03 Aug 2019 01:52:39 +0000 - rev 486063
Push 36380 by btara@mozilla.com at Sat, 03 Aug 2019 09:46:28 +0000
Bug 1570051 - Minor updates to android mach commands; r=bc Various cleanup: - remove extraneous calls to grant_runtime_permissions - remove unused legacy jimdb support code - remove "This may take a while" logging - emphasize x86/x86_64 capabilities of emulator Differential Revision: https://phabricator.services.mozilla.com/D40302
44ef2fe5a74b688484f3358d5d929cbea223085f: Bug 1568856 - Run android-hw jsreftest against geckoview; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 25 Jul 2019 20:23:22 +0000 - rev 484772
Push 36347 by csabou@mozilla.com at Fri, 26 Jul 2019 03:42:45 +0000
Bug 1568856 - Run android-hw jsreftest against geckoview; r=bc Switch android-hw jsreftest to geckoview. Technically this runs all android-hw reftests on geckoview -- I don't imagine we'll ever want to run any android-hw fennec reftests. Differential Revision: https://phabricator.services.mozilla.com/D39350
1e5df39ef4aaeadfe1bb61d2d6830d82e720a99e: Bug 1567332 - Report exception stack in android cppunit tests; r=bc
Geoff Brown <gbrown@mozilla.com> - Fri, 19 Jul 2019 14:23:10 +0000 - rev 483499
Push 36321 by malexandru@mozilla.com at Fri, 19 Jul 2019 21:56:14 +0000
Bug 1567332 - Report exception stack in android cppunit tests; r=bc print_exc() gives us information about the location of the failure and also ensures that the exception name is logged, which android-em task retries rely on. This also makes cppunit exception handling more consistent with other harnesses (mochitest, gtest, ...). Differential Revision: https://phabricator.services.mozilla.com/D38666
5616b96450dcd23cd16c4cebb099bfbc79c6b170: Bug 1561737 - Log full exception traceback from android gtest; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 27 Jun 2019 09:26:35 +0000 - rev 480351
Push 36211 by rmaries@mozilla.com at Thu, 27 Jun 2019 21:47:35 +0000
Bug 1561737 - Log full exception traceback from android gtest; r=bc Including the traceback info will include the exception name, like "ADBError" which should trigger the android-em task retry; it also provides more debugging info. Differential Revision: https://phabricator.services.mozilla.com/D36116
88737086fe42e08a37bda13eb040a3e770017987: Bug 1557152 - [mozdevice] Retry mkdir check for directory existence; r=bc
Geoff Brown <gbrown@mozilla.com> - Wed, 26 Jun 2019 22:45:11 +0000 - rev 480255
Push 36208 by ccoroiu@mozilla.com at Thu, 27 Jun 2019 09:34:48 +0000
Bug 1557152 - [mozdevice] Retry mkdir check for directory existence; r=bc This effectively avoids the mkdir failures I see with the 29.0.11 emulator on packet.net with Android 7.0 x86_64. I hate to add this sort of complication but it really helps clear the way for an otherwise useful upgrade. Differential Revision: https://phabricator.services.mozilla.com/D34740
6ec524b6ce7d620c8cca1c3d3b4295a72e3510d3: Bug 1558867 - Report log for short runs of 'mach gtest'; r=bc
Geoff Brown <gbrown@mozilla.com> - Wed, 12 Jun 2019 20:38:37 +0000 - rev 478542
Push 36145 by aciure@mozilla.com at Thu, 13 Jun 2019 03:50:31 +0000
Bug 1558867 - Report log for short runs of 'mach gtest'; r=bc This allows me to run 'mach gtest "APZ*"' and other short runs of gtest that were previously failing. Differential Revision: https://phabricator.services.mozilla.com/D34764
48fdaccbf5b8a1adf5e2805241cfdd4cd6892295: Bug 1558516 - [mozdevice] Improve check for effectiveness of rm; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 11 Jun 2019 15:23:22 +0000 - rev 478322
Push 36140 by dluca@mozilla.com at Wed, 12 Jun 2019 12:02:49 +0000
Bug 1558516 - [mozdevice] Improve check for effectiveness of rm; r=bc If path exists in any form after rm, rm() should raise. Differential Revision: https://phabricator.services.mozilla.com/D34531
0710791f6f52f2a3f64eeec64c6497337f183aa0: Bug 1557417 - Avoid cross-directory support file error in android mochitest; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 06 Jun 2019 21:47:04 +0000 - rev 477721
Push 36121 by dvarga@mozilla.com at Fri, 07 Jun 2019 09:47:19 +0000
Bug 1557417 - Avoid cross-directory support file error in android mochitest; r=bc Do not include the problematic manifest on Android. We never run Android mochitest-browser-chrome anyway. Bug 1435429 used a similar approach. Differential Revision: https://phabricator.services.mozilla.com/D34011
7b5f1a48d4e90a393618cd8e7302e22e7ea1d42b: Bug 1552300 - Support webreplay subsuite in test-verify; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 21 May 2019 13:26:09 +0000 - rev 474738
Push 36046 by aiakab@mozilla.com at Tue, 21 May 2019 21:45:52 +0000
Bug 1552300 - Support webreplay subsuite in test-verify; r=bc A new entry was required to map the subsuite name to the mozharness config name - simple! Differential Revision: https://phabricator.services.mozilla.com/D31522
8c8d7435dad6a4728cedb6ac714b88d981ed6b6c: Bug 1552052 - Do not dump mochitest/reftest logcat for successful runs; r=bc
Geoff Brown <gbrown@mozilla.com> - Wed, 15 May 2019 22:48:26 +0000 - rev 474005
Push 36020 by dvarga@mozilla.com at Thu, 16 May 2019 04:15:07 +0000
Bug 1552052 - Do not dump mochitest/reftest logcat for successful runs; r=bc Logcat is available as a separate artifact anyway. This makes the test log for successful runs much smaller: easier to read, cheaper to store. Differential Revision: https://phabricator.services.mozilla.com/D31357
71d1c36b3e1891c6876ab6273fec63b7bc7e3f90: Bug 1550828: String fixes and minor cleanup for power.py and Raptor's mach_commands.py. r=bc
Stephen Donner <stephen.donner@gmail.com> - Sat, 11 May 2019 08:13:29 +0000 - rev 473630
Push 36007 by apavel@mozilla.com at Mon, 13 May 2019 21:45:52 +0000
Bug 1550828: String fixes and minor cleanup for power.py and Raptor's mach_commands.py. r=bc Differential Revision: https://phabricator.services.mozilla.com/D30775
a22ba2fa077a0b0f9fc21bc0b1bcbb6737331f74: Bug 1549992 [mozdevice] mozdevice is not returning exception launch_application is returning a error r=bc
Florin Strugariu <fstrugariu@mozilla.com> - Thu, 09 May 2019 13:24:16 +0000 - rev 473385
Push 35996 by dvarga@mozilla.com at Fri, 10 May 2019 21:46:48 +0000
Bug 1549992 [mozdevice] mozdevice is not returning exception launch_application is returning a error r=bc Differential Revision: https://phabricator.services.mozilla.com/D30368
919f1307f466e0d747bcc5cc40947ddfb0d7662e: Bug 1550161 - Avoid attribute error in android gtest; r=bc
Geoff Brown <gbrown@mozilla.com> - Fri, 10 May 2019 01:19:43 +0000 - rev 473340
Push 35995 by apavel@mozilla.com at Fri, 10 May 2019 09:50:15 +0000
Bug 1550161 - Avoid attribute error in android gtest; r=bc Differential Revision: https://phabricator.services.mozilla.com/D30593
4e998aa9c04bf1dbce2087bfcf91ce8292fb7855: Bug 1548555 - For android gtest, push support files to device; r=bc
Geoff Brown <gbrown@mozilla.com> - Fri, 03 May 2019 17:45:21 +0000 - rev 472543
Push 35958 by malexandru@mozilla.com at Fri, 03 May 2019 21:56:39 +0000
Bug 1548555 - For android gtest, push support files to device; r=bc Differential Revision: https://phabricator.services.mozilla.com/D29837
9879ab660a34a9003a3242545fdc1989ee08addd: Bug 1250737 - Update android mozharness 'chunked' handling, for jittest; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 25 Apr 2019 21:17:59 +0000 - rev 471372
Push 35916 by rmaries@mozilla.com at Fri, 26 Apr 2019 09:46:15 +0000
Bug 1250737 - Update android mozharness 'chunked' handling, for jittest; r=bc It turns out there are several places where the change to suite 'jittest-chunked' causes problem. I am abandoning that approach. Desktop uses this trick, and this returns android '-chunked' handling to a state similar to what it was before I started messing around! Differential Revision: https://phabricator.services.mozilla.com/D28897
d1240d47e791648b1fafa798373ae12df02ea285: Bug 1546922 - Update tryselect unit test name for android jittest; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 25 Apr 2019 13:46:48 +0000 - rev 471317
Push 35915 by opoprus@mozilla.com at Thu, 25 Apr 2019 22:08:17 +0000
Bug 1546922 - Update tryselect unit test name for android jittest; r=bc Differential Revision: https://phabricator.services.mozilla.com/D28836
1fae6818d4e4185f914a8b7b39afc8d906a5e2d4: Bug 1492695 - Fix android-hw jittest suite name to avoid timeouts; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 25 Apr 2019 01:29:42 +0000 - rev 471232
Push 35912 by btara@mozilla.com at Thu, 25 Apr 2019 09:46:25 +0000
Bug 1492695 - Fix android-hw jittest suite name to avoid timeouts; r=bc I still haven't managed to verify this on try, but it seems like the best explanation for the timeouts. Differential Revision: https://phabricator.services.mozilla.com/D28762
ba2e784fcc836dfe7375d863de473f3e3c4a16fb: Bug 1545617: update mac host-utils r=bc,gbrown
Andrew Erickson <aerickson@mozilla.com> - Tue, 23 Apr 2019 08:26:12 +0000 - rev 470457
Push 35906 by aciure@mozilla.com at Tue, 23 Apr 2019 22:14:56 +0000
Bug 1545617: update mac host-utils r=bc,gbrown Differential Revision: https://phabricator.services.mozilla.com/D28249
a4fab3aaa82bf0f9bc23a827b369c51c4db0642d: Bug 1545617: update linux host-utils r=bc,gbrown
Andrew Erickson <aerickson@mozilla.com> - Mon, 22 Apr 2019 19:53:30 +0000 - rev 470456
Push 35906 by aciure@mozilla.com at Tue, 23 Apr 2019 22:14:56 +0000
Bug 1545617: update linux host-utils r=bc,gbrown Source push: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=74dc09642c222e18634f4f13e7b0bd6b7f91cbc2 Differential Revision: https://phabricator.services.mozilla.com/D28163
b3ff6570a179d4fdcc9ffce068f20d45be05cc44: Bug 1545860: fix tooltool url, r2 r=bc,gbrown
Andrew Erickson <aerickson@mozilla.com> - Mon, 22 Apr 2019 20:06:37 +0000 - rev 470410
Push 35905 by dvarga@mozilla.com at Tue, 23 Apr 2019 09:53:27 +0000
Bug 1545860: fix tooltool url, r2 r=bc,gbrown changes from https://phabricator.services.mozilla.com/D28260: - fix flake error ( was reverted due to one) Differential Revision: https://phabricator.services.mozilla.com/D28388
98df47a219e2088d431e3961fe6ea7f99017a1be: Bug 1318091 - Support |mach gtest| for android; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 22 Apr 2019 15:55:23 +0000 - rev 470362
Push 35903 by opoprus@mozilla.com at Mon, 22 Apr 2019 21:46:44 +0000
Bug 1318091 - Support |mach gtest| for android; r=bc Add basic support for 'mach gtest' on Android. Handling of Android-only and desktop-only options is awkward; I hope to re-visit this after bug 1519369. Differential Revision: https://phabricator.services.mozilla.com/D28129
f1cc15c2bd27c9f04c15a70a0fd71239156ec104: Bug 1546045 - [mozdevice] Downgrade 'chmod external storage' warning to debug message; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 22 Apr 2019 15:55:23 +0000 - rev 470361
Push 35903 by opoprus@mozilla.com at Mon, 22 Apr 2019 21:46:44 +0000
Bug 1546045 - [mozdevice] Downgrade 'chmod external storage' warning to debug message; r=bc Differential Revision: https://phabricator.services.mozilla.com/D28311
8701216ef356d0c20b96a80c49c8fd53a3572bc8: Bug 1544940 - [mozdevice] Fix typo in default intent name; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 16 Apr 2019 23:26:24 +0000 - rev 469816
Push 35883 by btara@mozilla.com at Wed, 17 Apr 2019 21:47:29 +0000
Bug 1544940 - [mozdevice] Fix typo in default intent name; r=bc Differential Revision: https://phabricator.services.mozilla.com/D27836
3e3f0733baa23b26d8b031ee0e0fb87fb0ae66e9: Bug 1318091 - Add more options to remotegtests.py; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 16 Apr 2019 17:47:58 +0000 - rev 469740
Push 35880 by cbrindusan@mozilla.com at Wed, 17 Apr 2019 09:36:19 +0000
Bug 1318091 - Add more options to remotegtests.py; r=bc Support --shuffle and <gtest_filter> for android gtest. Differential Revision: https://phabricator.services.mozilla.com/D27731
b8f49a14c458f56a6a08e4c177671108e386be3a: Bug 1474897: switch bitbar workers to g-w r=bc,tomprince
Andrew Erickson <aerickson@mozilla.com> - Mon, 15 Apr 2019 17:30:59 +0000 - rev 469534
Push 35873 by ccoroiu@mozilla.com at Mon, 15 Apr 2019 21:36:26 +0000
Bug 1474897: switch bitbar workers to g-w r=bc,tomprince Much of this was already reviewed in D21473 (my test change where I developed the payload modifications and that pointed tests at my test queue). This change keeps the payload changes from D21473, but points at the new 'real' queues we'll be using. Differential Revision: https://phabricator.services.mozilla.com/D25009
483960ad2be29aa30a348c57cd817532edc18d40: Bug 1318091 - Add Android 7.0 gtest tasks; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 11 Apr 2019 20:49:33 +0000 - rev 469291
Push 35861 by btara@mozilla.com at Fri, 12 Apr 2019 21:56:33 +0000
Bug 1318091 - Add Android 7.0 gtest tasks; r=bc Add Android 7.0 gtests, opt and debug, running against the geckoview TestRunnerActivity. Differential Revision: https://phabricator.services.mozilla.com/D27016
5bd741206a8b3917a7b34298e841b750aa9bc1cb: Bug 1318091 - Add remotegtests.py, supporting android gtests; r=bc
Geoff Brown <gbrown@mozilla.com> - Fri, 12 Apr 2019 15:04:39 +0000 - rev 469290
Push 35861 by btara@mozilla.com at Fri, 12 Apr 2019 21:56:33 +0000
Bug 1318091 - Add remotegtests.py, supporting android gtests; r=bc Adds remotegtests.py, like rungtests.py, but for Android. Unlike some other test harnesses, remotegtests is not a sub-class of rungtests: There wasn't much code that could be re-used. The code to wait for the test app and collect and display the log is derived from and similar to existing code in remoteautomation.py: I didn't want to increase reliance on remoteautomation; I don't mind a bit of code duplication. There is a TODO item related to libxul.so. gtest runs in the browser, but with tests compiled into a gtest-specific version of libxul.so. remotegtests.py patches the installed app by pushing the libxul.so to the installation directory of the app -- root required and fragile, but works fine on the emulator. I think the "right" way to do this is to create a gtest-specific apk; I plan to file a follow-up bug and petition build folks to help sort that out. I have been running this locally with: mach gtest (builds gtests, then errors out) mach python testing/gtest/remotegtests.py --libxul=/home/gbrown/objdirs/x86_64/dist/bin/gtest/libxul.so Work-in-progress on 'mach gtest' will make this much simpler. Differential Revision: https://phabricator.services.mozilla.com/D26835
60a543a89dfa78df3b8dfcb8c3838f7df9412b36: Bug 1318091 - Skip jemalloc gtests on android; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 11 Apr 2019 10:57:50 +0000 - rev 468991
Push 35856 by csabou@mozilla.com at Fri, 12 Apr 2019 03:19:48 +0000
Bug 1318091 - Skip jemalloc gtests on android; r=bc The jemalloc tests leave behind minidumps. Disable for now, for a green run. Differential Revision: https://phabricator.services.mozilla.com/D27014
64deb410ad6894ec356f12c8c9b40a9a36996c0e: Bug 1318091 - Support logging to file in mozilla gtest; r=bc,Ehsan
Geoff Brown <gbrown@mozilla.com> - Wed, 10 Apr 2019 22:11:48 +0000 - rev 468900
Push 35854 by aciure@mozilla.com at Thu, 11 Apr 2019 09:50:57 +0000
Bug 1318091 - Support logging to file in mozilla gtest; r=bc,Ehsan On Android, update mozilla gtest logging so that logging appears in the Android logcat. Also, when MOZ_GTEST_LOG_PATH is defined in the environment, create the named file and direct logging to that file. Android gtest will use this to collect gtest logging from the device and copy it to the test log. Differential Revision: https://phabricator.services.mozilla.com/D26610
9eb55c9bf557d9b683d4808620e26da6e242c4b0: Bug 1532695 - Include target.gtest.tests.tar.gz in android builds; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 08 Apr 2019 22:02:45 +0000 - rev 468440
Push 35837 by rmaries@mozilla.com at Tue, 09 Apr 2019 03:43:40 +0000
Bug 1532695 - Include target.gtest.tests.tar.gz in android builds; r=bc Differential Revision: https://phabricator.services.mozilla.com/D26587
c87d5720c98201317c94bf8655a07f32fb188e00: Bug 1318091 - Disable failing android gtests; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 08 Apr 2019 20:58:21 +0000 - rev 468429
Push 35837 by rmaries@mozilla.com at Tue, 09 Apr 2019 03:43:40 +0000
Bug 1318091 - Disable failing android gtests; r=bc Disable gtests observed to fail on Android. Some of these are simple build failures and failures due to file permissions or paths, while other failures are more obscure. Once Android gtests are running on mozilla-central, I will file follow-up bugs inviting teams to investigate the failures and re-enable Android gtests that are important to them. Differential Revision: https://phabricator.services.mozilla.com/D26606
b1571c5221831c10d481fec95bdb889bfd32e7b4: Bug 1532695 - Include target.gtest.tests.tar.gz in android builds; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 08 Apr 2019 20:16:43 +0000 - rev 468414
Push 35837 by rmaries@mozilla.com at Tue, 09 Apr 2019 03:43:40 +0000
Bug 1532695 - Include target.gtest.tests.tar.gz in android builds; r=bc Differential Revision: https://phabricator.services.mozilla.com/D26587
63888044e37b35be11f43be8b10b0a17055e9a6d: Bug 1532491 - Part 3: Enable running AWSY tp6 in automation. r=bc
Eric Rahm <erahm@mozilla.com> - Fri, 29 Mar 2019 19:35:24 +0000 - rev 467441
Push 35799 by cbrindusan@mozilla.com at Tue, 02 Apr 2019 08:35:12 +0000
Bug 1532491 - Part 3: Enable running AWSY tp6 in automation. r=bc An `sy-tp6` variant is added to the AWSY test suite that runs against the tp6 pageset. Differential Revision: https://phabricator.services.mozilla.com/D24585
b7a77be421d17781c2787306c7b9cf8571ab7cbd: Bug 1532491 - Part 2: Add a tp6 version of AWSY. r=bc,rwood
Eric Rahm <erahm@mozilla.com> - Mon, 01 Apr 2019 19:21:54 +0000 - rev 467440
Push 35799 by cbrindusan@mozilla.com at Tue, 02 Apr 2019 08:35:12 +0000
Bug 1532491 - Part 2: Add a tp6 version of AWSY. r=bc,rwood This adds a '--tp6' option to `mach awsy-test` which allows the running of the AWSY test against the tp6 pageset rather than the default tp5 pageset. Differential Revision: https://phabricator.services.mozilla.com/D23606
d4b81226b56e9a914d6b553f681b51b3c5aa7fb7: Bug 1532491 - Part 1: Always check for a new tab handle. r=bc
Eric Rahm <erahm@mozilla.com> - Fri, 29 Mar 2019 20:12:17 +0000 - rev 467439
Push 35799 by cbrindusan@mozilla.com at Tue, 02 Apr 2019 08:35:12 +0000
Bug 1532491 - Part 1: Always check for a new tab handle. r=bc It's possible for the first tab handle to change as well. This removes the special case for when we only add a new tab and just checks all the time. Differential Revision: https://phabricator.services.mozilla.com/D25327
97e3dbc87ce9de4e5a4da5477bb95e5022ae3387: Bug 1534778. Abstract and enable power tests for non-GeckoView browsers. r=rwood,bc
Stephen Donner <stephen.donner@gmail.com> - Fri, 29 Mar 2019 18:47:35 +0000 - rev 467016
Push 35793 by opoprus@mozilla.com at Mon, 01 Apr 2019 09:46:51 +0000
Bug 1534778. Abstract and enable power tests for non-GeckoView browsers. r=rwood,bc Differential Revision: https://phabricator.services.mozilla.com/D24971
76fd580f28620e5a6f56856d5c2bfea2ab11539e: Bug 1538675 - transform Android pgo test platform names so they show up as using 'pgo' as option on Treeherder r=bc
Sebastian Hengst <archaeopteryx@coole-files.de> - Thu, 28 Mar 2019 16:29:10 +0000 - rev 466598
Push 35773 by ncsoregi@mozilla.com at Fri, 29 Mar 2019 04:11:36 +0000
Bug 1538675 - transform Android pgo test platform names so they show up as using 'pgo' as option on Treeherder r=bc Differential Revision: https://phabricator.services.mozilla.com/D25091
15abc6d9064754807267c7ccbaa9ba0b4ca2b5ab: Bug 1536640 - Improve MOZ_LOG support in Android mochitest harness; r=bc
Geoff Brown <gbrown@mozilla.com> - Mon, 25 Mar 2019 14:55:20 +0000 - rev 465944
Push 35755 by cbrindusan@mozilla.com at Tue, 26 Mar 2019 00:24:34 +0000
Bug 1536640 - Improve MOZ_LOG support in Android mochitest harness; r=bc Unifies the mochitest MOZ_LOG file naming and archiving across desktop/android. Notably the inclusion of pid and uuid for android log files helps generate appropriate files for e10s on geckoview. Differential Revision: https://phabricator.services.mozilla.com/D24262
981a62a09810bbe2e051687b8831af4972427649: Bug 1529238 - Avoid TypeError in 'mach test <reftest> --verify'; r=bc
Geoff Brown <gbrown@mozilla.com> - Fri, 22 Mar 2019 19:52:07 +0000 - rev 465772
Push 35746 by shindli@mozilla.com at Sat, 23 Mar 2019 09:46:24 +0000
Bug 1529238 - Avoid TypeError in 'mach test <reftest> --verify'; r=bc Remove the troublesome log options once they have been used. Differential Revision: https://phabricator.services.mozilla.com/D24525
578d02d4113982fc5e7071b88a9165605d1be150: Bug 632954 - Ignore dashes in adb error messages; r=bc
Mike Shal <mshal@mozilla.com> - Mon, 18 Mar 2019 23:53:15 +0000 - rev 465184
Push 35735 by shindli@mozilla.com at Thu, 21 Mar 2019 04:34:45 +0000
Bug 632954 - Ignore dashes in adb error messages; r=bc The regex should match '-' characters as well as \w to properly trim the error message if the device string contains a dash. Differential Revision: https://phabricator.services.mozilla.com/D22823
26031d3623333bbdedd1fb388f0867bc9f7cc23c: Bug 632954 - Ignore dashes in adb error messages; r=bc
Mike Shal <mshal@mozilla.com> - Mon, 18 Mar 2019 23:53:15 +0000 - rev 465141
Push 35732 by opoprus@mozilla.com at Wed, 20 Mar 2019 10:52:37 +0000
Bug 632954 - Ignore dashes in adb error messages; r=bc The regex should match '-' characters as well as \w to properly trim the error message if the device string contains a dash. Differential Revision: https://phabricator.services.mozilla.com/D22823
f45661298ac32d7f9dc451bd1d1a703a45abffd0: Bug 1535417 - Set dynamic mozinfo fields in Android test-verify; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 19 Mar 2019 18:11:44 +0000 - rev 465076
Push 35732 by opoprus@mozilla.com at Wed, 20 Mar 2019 10:52:37 +0000
Bug 1535417 - Set dynamic mozinfo fields in Android test-verify; r=bc In the mochitest harness, is_fennec is populated by examining harness options, and is_emulator and android_version are populated by examining the device via mozdevice. The per-test code doesn't have those options and the emulator may not be available yet, so I've opted for populated those fields from mozharness configuration. In practice, we only run Android TV on Android 4.3, where is_fennec=True, is_emulator=True, and android_version=18. I'd like to run TV on Android 7.0/geckoview eventually, where is_fennec=False, is_emulator=True, and android_version=24. Since I was here, I also removed 'stylo' from the per-test mozinfo, since that field is obsolete now. Differential Revision: https://phabricator.services.mozilla.com/D23595
8130ba1701bbd69ec304eca887c0e66e9e1307ef: Bug 1526654 - Use xpcshell sequential mode consistently when running a single test; r=bc
Geoff Brown <gbrown@mozilla.com> - Wed, 13 Mar 2019 06:14:52 +0000 - rev 463810
Push 35698 by ncsoregi@mozilla.com at Wed, 13 Mar 2019 21:52:48 +0000
Bug 1526654 - Use xpcshell sequential mode consistently when running a single test; r=bc In the harness, sequential mode is set when self.singleFile is set. self.singleFile has been set correctly when a single test is specified as a test_path (mach xpcshell-test <test>) but it has not been set correctly if a single test is specified in a manifest (mach test <test); this patch corrects for that by setting self.singleFile after all test specifications have set self.alltests. An unintended consequence of the code rearrangement is that the chunk_by_slice filter is now used even when self.singleFile would be set -- but only if totalChunks > 1; this situation seems very unlikely, and the consequences minimal. Differential Revision: https://phabricator.services.mozilla.com/D23253
1aa0df07fbddd6007b3a8023e32509b55aabdc46: Bug 1533517 - [mozdevice] Remove FirefoxOS candidate test root paths. r=bc
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 12 Mar 2019 13:55:51 +0000 - rev 463637
Push 35691 by nbeleuzu@mozilla.com at Tue, 12 Mar 2019 21:43:52 +0000
Bug 1533517 - [mozdevice] Remove FirefoxOS candidate test root paths. r=bc Differential Revision: https://phabricator.services.mozilla.com/D22952
3fd4a7b0872e76f8396355a1811676dcfbd86a79: Bug 1533445 - Make android tests shutdown faster when device unresponsive; r=bc
Geoff Brown <gbrown@mozilla.com> - Thu, 07 Mar 2019 22:45:13 +0000 - rev 463060
Push 35665 by shindli@mozilla.com at Fri, 08 Mar 2019 09:39:15 +0000
Bug 1533445 - Make android tests shutdown faster when device unresponsive; r=bc Differential Revision: https://phabricator.services.mozilla.com/D22610
664638fa249e1d9ba53fb82acd8c72e96affb234: Bug 1532462 - Avoid permission error in Android cppunittests on some devices by creating destination directory; r=bc
Geoff Brown <gbrown@mozilla.com> - Tue, 05 Mar 2019 17:03:27 +0000 - rev 462420
Push 35652 by shindli@mozilla.com at Wed, 06 Mar 2019 04:36:55 +0000
Bug 1532462 - Avoid permission error in Android cppunittests on some devices by creating destination directory; r=bc Differential Revision: https://phabricator.services.mozilla.com/D22034