Index: scripts/slave/recipes/bisect_test/example_bisect_results.expected/failed_direction_test.json |
diff --git a/scripts/slave/recipes/bisect_test/example_bisect_results.expected/failed_direction_test.json b/scripts/slave/recipes/bisect_test/example_bisect_results.expected/failed_direction_test.json |
index e6a6865b23c044be57951a12b75560f1af9cb306..23403761e783d538bfcdab1b8129a2c760d7734d 100644 |
--- a/scripts/slave/recipes/bisect_test/example_bisect_results.expected/failed_direction_test.json |
+++ b/scripts/slave/recipes/bisect_test/example_bisect_results.expected/failed_direction_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/perf/run_benchmark -v --browser=release smoothness.tough_scrolling_cases\", \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 match the expected direction of improvement. Thus, likely represent an improvement and not a regression.\nPlease contact the the team (see below) if you believe this is in error.\n\nBug ID: \n\nTest Command: src/tools/perf/run_benchmark -v --browser=release smoothness.tough_scrolling_cases\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:\nsrc/tools/perf/run_benchmark -v --browser=<bot-name> smoothness.tough_scrolling_cases\n(Where <bot-name> comes from tools/perf/run_benchmark --browser=list)\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." |
} |