|
|
Created:
3 years, 7 months ago by mikecase (-- gone --) Modified:
3 years, 7 months ago CC:
chromium-reviews Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionSpecify --gs-results-bucket arg for chromium.android bots.
This should trigger these bots to start uploading screenshots
of test failures as well as uploading render test results in the
future.
Review-Url: https://codereview.chromium.org/2868943002
Cr-Commit-Position: refs/heads/master@{#471565}
Committed: https://chromium.googlesource.com/chromium/src/+/9116a0309166e8868dddc39014d2eb51951305cb
Patch Set 1 #Patch Set 2 : Specify --gs-results-bucket arg for chromium.android bots. #
Total comments: 2
Patch Set 3 : Fixed mistake #Patch Set 4 : REBASE #Messages
Total messages: 29 (12 generated)
mikecase@chromium.org changed reviewers: + hzl@chromium.org, jbudorick@chromium.org
This should enable screenshot-failure capturing on the bots on chromium.android. I havent done much with these configs, but I think this is right.
https://codereview.chromium.org/2868943002/diff/20001/testing/buildbot/chromi... File testing/buildbot/chromium.android.json (right): https://codereview.chromium.org/2868943002/diff/20001/testing/buildbot/chromi... testing/buildbot/chromium.android.json:3361: "--gs-results-bucket=chromium-result-details" This is the only gtest suite to which you're adding this argument. Why? I'd leave it to just instrumentation tests.
Fixed. https://codereview.chromium.org/2868943002/diff/20001/testing/buildbot/chromi... File testing/buildbot/chromium.android.json (right): https://codereview.chromium.org/2868943002/diff/20001/testing/buildbot/chromi... testing/buildbot/chromium.android.json:3361: "--gs-results-bucket=chromium-result-details" On 2017/05/08 at 23:04:41, jbudorick wrote: > This is the only gtest suite to which you're adding this argument. Why? I'd leave it to just instrumentation tests. Definitely a mistake. Fixed
jbudorick@google.com changed reviewers: + jbudorick@google.com
lgtm
On 2017/05/10 20:34:45, wrong jbudorick wrote: > lgtm also lgtm
The CQ bit was checked by mikecase@chromium.org
Hoping this works!
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: android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...) android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...) linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by mikecase@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from jbudorick@chromium.org, jbudorick@google.com Link to the patchset: https://codereview.chromium.org/2868943002/#ps60001 (title: "REBASE")
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: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
waaaah, why won't anything get thru the CQ
The CQ bit was checked by mikecase@chromium.org
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: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by mikecase@chromium.org
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Might have to commit this with NOTRY=true, the linux_chromium_asan_rel_ng bot is broken.
CQ is committing da patch. Bot data: {"patchset_id": 60001, "attempt_start_ts": 1494649132720500, "parent_rev": "f556cef44f474c02e486e7c3e4eec685dc50794c", "commit_rev": "9116a0309166e8868dddc39014d2eb51951305cb"}
Message was sent while issue was closed.
Description was changed from ========== Specify --gs-results-bucket arg for chromium.android bots. This should trigger these bots to start uploading screenshots of test failures as well as uploading render test results in the future. ========== to ========== Specify --gs-results-bucket arg for chromium.android bots. This should trigger these bots to start uploading screenshots of test failures as well as uploading render test results in the future. Review-Url: https://codereview.chromium.org/2868943002 Cr-Commit-Position: refs/heads/master@{#471565} Committed: https://chromium.googlesource.com/chromium/src/+/9116a0309166e8868dddc39014d2... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/chromium/src/+/9116a0309166e8868dddc39014d2...
Message was sent while issue was closed.
A revert of this CL (patchset #4 id:60001) has been created in https://codereview.chromium.org/2878033003/ by mikecase@chromium.org. The reason for reverting is: Need to list jinja template as data dep for python script. Swaaaarrrrmmmiiinngg!. |