Fix auto-unittest compile target
Since the inspector_overlay moved, we also moved the karma.conf.js.
However, `npm run auto-unittest` was not properly building the
karma configuration file, as that was moved into its parent
directory.
R=alexrudenko@chromium.org
CC=aerotwist@chromium.org
Change-Id: Ic74c01632fb28de6afe70e0d8555e79f97bbdb33
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2401017
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
diff --git a/scripts/test/run_auto_unittests.py b/scripts/test/run_auto_unittests.py
index bd608f2..fc9b154 100644
--- a/scripts/test/run_auto_unittests.py
+++ b/scripts/test/run_auto_unittests.py
@@ -36,7 +36,7 @@
help='Whether to output coverage')
args = parser.parse_args(sys.argv[1:])
- efficiently_recompile.recompile(args.target, 'test/unittests/front_end')
+ efficiently_recompile.recompile(args.target, 'test/unittests')
run_unittests.run_unit_tests_on_ninja_build_target(args.target,
args.no_text_coverage,
args.coverage)