|
|
DescriptionShow stdout of command run by run_gtest_perf_test.py script
Before this, we don't have stdout of C++ benchmarks run printed in the log,
which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12)
TBR=eyaich@chromium.org
BUG=715565
NOTRY=true
Review-Url: https://codereview.chromium.org/2871823003
Cr-Commit-Position: refs/heads/master@{#470528}
Committed: https://chromium.googlesource.com/chromium/src/+/081c413ed0a7e406c27efe67d17f40705aa07ed1
Patch Set 1 #
Messages
Total messages: 34 (22 generated)
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. TBR=eyaich@chromium.org BUG=715565 ========== to ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 ==========
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 ========== to ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true ==========
On 2017/05/09 22:29:20, commit-bot: I haz the power wrote: > CQ is trying da patch. > > Follow status at: > https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... Added NOTRY because the CQ kept being blocked for unrelated failure.
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true ========== to ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true NOPRESUBMIT=true ==========
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true NOPRESUBMIT=true ========== to ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=1 ==========
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=1 ========== to ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true ==========
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 1, "attempt_start_ts": 1494410177343080, "parent_rev": "7bf282aee6c77b7142d25900d5fd42c822a6d24d", "commit_rev": "081c413ed0a7e406c27efe67d17f40705aa07ed1"}
Message was sent while issue was closed.
Description was changed from ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true ========== to ========== Show stdout of command run by run_gtest_perf_test.py script Before this, we don't have stdout of C++ benchmarks run printed in the log, which makes debugging hard. (See https://bugs.chromium.org/p/chromium/issues/detail?id=704211#c12) TBR=eyaich@chromium.org BUG=715565 NOTRY=true Review-Url: https://codereview.chromium.org/2871823003 Cr-Commit-Position: refs/heads/master@{#470528} Committed: https://chromium.googlesource.com/chromium/src/+/081c413ed0a7e406c27efe67d17f... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/081c413ed0a7e406c27efe67d17f... |