Fix negative gtest filters for instrumentation tests |
||
Issue descriptionNegative gtest filters (e.g. -org.chromium.test.FooTest) don't currently work because we try to support filters both with and without package names.
,
Dec 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7ea0ee47f0a67a13f8ac46d8ab1c15f8abba8ac4 commit 7ea0ee47f0a67a13f8ac46d8ab1c15f8abba8ac4 Author: mikecase <mikecase@chromium.org> Date: Thu Dec 15 20:39:51 2016 Fix negative gtest filters for instrumentation tests. BUG= 623047 Review-Url: https://codereview.chromium.org/2580943002 Cr-Commit-Position: refs/heads/master@{#438914} [modify] https://crrev.com/7ea0ee47f0a67a13f8ac46d8ab1c15f8abba8ac4/build/android/pylib/instrumentation/instrumentation_test_instance.py [modify] https://crrev.com/7ea0ee47f0a67a13f8ac46d8ab1c15f8abba8ac4/build/android/pylib/instrumentation/instrumentation_test_instance_test.py
,
Dec 15 2016
This should be fixed now. |
||
►
Sign in to add a comment |
||
Comment 1 by jbudorick@chromium.org
, Dec 15 2016Status: Assigned (was: Available)