Lean on constraints more heavily for m4f targets
We want to have the CI script test //... and have bazel sort out the
rest rather than keep a target list up to date by hand.
Change-Id: I1ab48b8d115fd878fecdd87b00f8221712061ab0
diff --git a/tools/ci/run-tests.sh b/tools/ci/run-tests.sh
index 24cdc5b..f39492d 100755
--- a/tools/ci/run-tests.sh
+++ b/tools/ci/run-tests.sh
@@ -3,7 +3,7 @@
set -x
readonly TARGETS='//... @com_github_google_glog//... @com_google_ceres_solver//...'
-readonly M4F_TARGETS='//motors/... //y2019/jevois/...'
+readonly M4F_TARGETS='//...'
readonly COMMON='-c opt --stamp=no --curses=no --color=no --symlink_prefix=/'
# Put everything in different output bases so we can get 4 bazel servers