|
|
Created:
4 years, 10 months ago by ghost stip (do not use) Modified:
4 years, 10 months ago CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionSrc-ify Android Tests.
build-side is here: https://codereview.chromium.org/1645723004/
BUG=525873
Committed: https://crrev.com/4abea28bed4a20fb89a1fc65eafcfb772ce0ca0f
Cr-Commit-Position: refs/heads/master@{#372108}
Patch Set 1 #
Total comments: 1
Patch Set 2 : Add isolate arguments to gtest spec. #
Total comments: 4
Patch Set 3 : Fix isolate file. #Messages
Total messages: 39 (16 generated)
Description was changed from ========== Src-ify Android Tests. BUG=525873 ========== to ========== Src-ify Android Tests. BUG=525873 ==========
stip@chromium.org changed reviewers: + dpranke@chromium.org, jbudorick@chromium.org
Description was changed from ========== Src-ify Android Tests. BUG=525873 ========== to ========== Src-ify Android Tests. build-side is here: https://codereview.chromium.org/1645723004/ BUG=525873 ==========
ptal
https://codereview.chromium.org/1649593002/diff/1/testing/buildbot/chromium.l... File testing/buildbot/chromium.linux.json (right): https://codereview.chromium.org/1649593002/diff/1/testing/buildbot/chromium.l... testing/buildbot/chromium.linux.json:146: "test": "base_unittests" non-swarming tests don't use the wrapper scripts at the moment, so you have to pass the --isolate-file-path explicitly: https://code.google.com/p/chromium/codesearch#chromium/src/testing/buildbot/c...
updated, ptal
lgtm I'm guessing you're going to address the instrumentation tests separately?
yeah, I haven't src-ed them yet. my initial goal is to get a few gtests running in production
lgtm
https://codereview.chromium.org/1649593002/diff/20001/testing/buildbot/chromi... File testing/buildbot/chromium.linux.json (right): https://codereview.chromium.org/1649593002/diff/20001/testing/buildbot/chromi... testing/buildbot/chromium.linux.json:240: "--isolate_file_path=src/ui/base/ui_base_unittests.isolate" this should be ui_base_tests.isolate https://codereview.chromium.org/1649593002/diff/20001/testing/buildbot/chromi... testing/buildbot/chromium.linux.json:372: "--isolate_file_path=src/ui/base/ui_base_unittests.isolate" same
https://codereview.chromium.org/1649593002/diff/20001/testing/buildbot/chromi... File testing/buildbot/chromium.linux.json (right): https://codereview.chromium.org/1649593002/diff/20001/testing/buildbot/chromi... testing/buildbot/chromium.linux.json:240: "--isolate_file_path=src/ui/base/ui_base_unittests.isolate" On 2016/01/28 04:27:37, jbudorick wrote: > this should be ui_base_tests.isolate Done. https://codereview.chromium.org/1649593002/diff/20001/testing/buildbot/chromi... testing/buildbot/chromium.linux.json:372: "--isolate_file_path=src/ui/base/ui_base_unittests.isolate" On 2016/01/28 04:27:37, jbudorick wrote: > same Done.
The CQ bit was checked by stip@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1649593002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1649593002/40001
tandrii@chromium.org changed reviewers: + tandrii@chromium.org
lgtm
The CQ bit was unchecked by stip@chromium.org
The CQ bit was checked by stip@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jbudorick@chromium.org Link to the patchset: https://codereview.chromium.org/1649593002/#ps40001 (title: "Fix isolate file.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1649593002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1649593002/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_asan_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by stip@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1649593002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1649593002/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_asan_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by tandrii@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1649593002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1649593002/40001
The failure both time is the same, but i have no idea as to why. I've reluctantly scheduled 3rd cq run, but I suspect the test is genuinely failing, and maybe it's mistakenly enabled in this CL.
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_asan_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by stip@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1649593002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1649593002/40001
Message was sent while issue was closed.
Description was changed from ========== Src-ify Android Tests. build-side is here: https://codereview.chromium.org/1645723004/ BUG=525873 ========== to ========== Src-ify Android Tests. build-side is here: https://codereview.chromium.org/1645723004/ BUG=525873 ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Src-ify Android Tests. build-side is here: https://codereview.chromium.org/1645723004/ BUG=525873 ========== to ========== Src-ify Android Tests. build-side is here: https://codereview.chromium.org/1645723004/ BUG=525873 Committed: https://crrev.com/4abea28bed4a20fb89a1fc65eafcfb772ce0ca0f Cr-Commit-Position: refs/heads/master@{#372108} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/4abea28bed4a20fb89a1fc65eafcfb772ce0ca0f Cr-Commit-Position: refs/heads/master@{#372108}
Message was sent while issue was closed.
4th time's the charm
Message was sent while issue was closed.
On 2016/01/28 16:53:22, stip wrote: > 4th time's the charm :(((
Message was sent while issue was closed.
A revert of this CL (patchset #3 id:40001) has been created in https://codereview.chromium.org/1643803004/ by stip@chromium.org. The reason for reverting is: build presubmit flake broke the build side test, so we can't double test. will reland later. |