PlzNavigate: adds Linux runs of content_browsertests to the CQ.

testing/buildbot/chromium.linux.json

Index: testing/buildbot/chromium.linux.json
diff --git a/testing/buildbot/chromium.linux.json b/testing/buildbot/chromium.linux.json
index 372102c223443e4258ea7119291e49ec5501dc11..c4c40736e8e1c5bdba64b7d46ea74f1b7d17d546 100644
--- a/testing/buildbot/chromium.linux.json
+++ b/testing/buildbot/chromium.linux.json
@@ -1057,6 +1057,17 @@
         "test": "content_browsertests"
       },
       {
+        "args": [
+          "--enable-browser-side-navigation",
+          "--test-launcher-filter-file=src/testing/buildbot/filters/browser-side-navigation.linux.content_browsertests.filter"

[Dirk Pranke, 2016/06/24 01:57:44]

I think this path is wrong. When you run binaries under swarming, the current
working directory is out/Release, and so this needs to be
"--test-launcher-filter-file=../../testing/buildbot/etc".

[carlosk, 2016/06/24 12:40:21]

Indeed that worked.

Now I'm puzzled: there is a similar reference to a cast filter file at line 845,
also for a swarming enabled content_browsertests run, and it uses that same
initial path structure. How come that one works?

[Dirk Pranke, 2016/06/24 23:37:27]

Despite the fact that it says that "can_use_on_swarming_builders": true in that
entry,
the test isn't actually being run under swarming. When it's run locally, the CWD
is the build directory,
and so that works. And, yes, it's really a flaw that we use different CWDs in
the two scenarios because
it'll break things like this.

+        ],
+        "name": "browser_side_navigation_content_browsertests",
+        "swarming": {
+          "can_use_on_swarming_builders": true
+        },
+        "test": "content_browsertests"
+      },
+      {
         "override_compile_targets": [
           "content_site_isolation_browsertests"
         ],