Recipes: make cwd default to slave_build

scripts/slave/recipes/bisect_test/example_bisect_results.expected/aborted_non_telemetry_test.json

Index: scripts/slave/recipes/bisect_test/example_bisect_results.expected/aborted_non_telemetry_test.json
diff --git a/scripts/slave/recipes/bisect_test/example_bisect_results.expected/aborted_non_telemetry_test.json b/scripts/slave/recipes/bisect_test/example_bisect_results.expected/aborted_non_telemetry_test.json
index 658752d296373cf165593070519d678fe8931132..38db16c345aa841161b7c775457c87868655f70f 100644
--- a/scripts/slave/recipes/bisect_test/example_bisect_results.expected/aborted_non_telemetry_test.json
+++ b/scripts/slave/recipes/bisect_test/example_bisect_results.expected/aborted_non_telemetry_test.json
@@ -4,6 +4,7 @@
       "echo",
       "{\n  \"bad_revision\": \"314017\", \n  \"bug_id\": \"\", \n  \"builder_host\": \"master4.golo.chromium.org\", \n  \"builder_port\": \"8341\", \n  \"command\": \"src/tools/dummy_command\", \n  \"dummy_builds\": \"True\", \n  \"good_revision\": \"314015\", \n  \"gs_bucket\": \"chrome-perf\", \n  \"max_time_minutes\": \"5\", \n  \"metric\": \"mean_input_event_latency/mean_input_event_latency\", \n  \"repeat_count\": \"2\", \n  \"skip_gclient_ops\": \"True\", \n  \"test_type\": \"perf\", \n  \"truncate_percent\": \"0\"\n}"
     ],
+    "cwd": "[SLAVE_BUILD]",
     "name": "config"
   },
   {
@@ -60,6 +61,7 @@
     "cmd": [
       "cat"
     ],
+    "cwd": "[SLAVE_BUILD]",
     "name": "Results",
     "stdin": "\n===== BISECTION ABORTED =====\nThe bisect was aborted because The metric values for the initial \"good\" and \"bad\" revisions do not represent a clear regression.\nPlease contact the the team (see below) if you believe this is in error.\n\nBug ID: \n\nTest Command: src/tools/dummy_command\nTest Metric: mean_input_event_latency/mean_input_event_latency\nGood revision: c001c0de\nBad revision: deadbeef\n\n\n===== WARNINGS =====\nThe following warnings were raised by the bisect job:\n\n * This is a demo warning\n\n\n===== TESTED REVISIONS =====\ncommit_pos revision_string mean_value std_err good_or_bad? tested? culprit? \n\n\n\n==== INSTRUCTIONS TO REPRODUCE ====\nTo run locally:\n - Use the test command given under 'BISECT JOB RESULTS' above.\n - Consider using a profiler. Pass --profiler=list to list available profilers.\n\n\nTo reproduce on a performance try bot:\n 1. Edit run-perf-test.cfg\n 2. $ git try -b <bot> --svn_repo='svn://svn.chromium.org/chrome-try/try-perf'\n\nNotes:\n a) Follow the in-file instructions in run-perf-test.cfg.\n b) run-perf-test.cfg is under tools/ or under third_party/WebKit/Tools.\n c) Do your edits preferably under a new git branch.\n d) --browser=release and --browser=android-chromium-testshell are supported\n    depending on the platform (desktop|android).\n e) Strip any src/ directories from the head of relative path names.\n f) Make sure to use the appropriate bot on step 3.\n\nFor more details please visit\nhttps://sites.google.com/a/chromium.org/dev/developers/performance-try-bots\n\n\n| O O | Visit http://www.chromium.org/developers/core-principles for Chrome's\n|  X  | policy on perf regressions. Contact chrome-perf-dashboard-team with any\n| / \\ | questions or suggestions about bisecting. THANK YOU."
   }