|
|
Created:
4 years, 9 months ago by tandrii(chromium) Modified:
4 years, 9 months ago CC:
chromium-reviews, dpranke+depot_tools_chromium.org, iannucci+depot_tools_chromium.org Base URL:
https://chromium.googlesource.com/chromium/tools/depot_tools.git@master Target Ref:
refs/heads/master Project:
depot_tools Visibility:
Public. |
Descriptiontesting_support: fix Gerrit releases URL.
R=szager@chromium.org,sergiyb@chromium.org
BUG=579160
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299408
Patch Set 1 #
Total comments: 1
Messages
Total messages: 13 (4 generated)
The CQ bit was checked by tandrii@chromium.org to run a CQ dry run
The CQ bit was unchecked by tandrii@chromium.org
PTAL Stephan, is that a good idea to use this OR would you rather recommend to burn this code with fire?
On 2016/03/21 15:54:34, tandrii(chromium) wrote: > PTAL > > Stephan, is that a good idea to use this OR would you rather recommend to burn > this code with fire? It used to be the case that tests using this script were the only test coverage we had to test infra code against the most recent version of gerrit. I have no idea if those tests are still running or not. At some point, the gerrit team started running the chromite tests against their staging server before they pushed to production (dborowitz knows more about this). If that's still happening, then it's good protection against breaking gerrit changes, but it doesn't provide coverage against breaking chrome infra changes. So... up to you, really. In my opinion, it's prudent to have test coverage to prevent chrome infra changes from breaking due to incompatibilities with gerrit.
lgtm
On 2016/03/21 16:56:35, Sergiy Byelozyorov wrote: > lgtm https://memegen.googleplex.com/5386850802860032
On 2016/03/21 16:55:38, szager1 wrote: > On 2016/03/21 15:54:34, tandrii(chromium) wrote: > > PTAL > > > > Stephan, is that a good idea to use this OR would you rather recommend to burn > > this code with fire? > > It used to be the case that tests using this script were the only test coverage > we had to test infra code against the most recent version of gerrit. I have no > idea if those tests are still running or not. > > At some point, the gerrit team started running the chromite tests against their > staging server before they pushed to production (dborowitz knows more about > this). If that's still happening, then it's good protection against breaking > gerrit changes, but it doesn't provide coverage against breaking chrome infra > changes. I see. ACtually they stopped just last week or so. But it'd like to ensure some end-to-end testing of "git cl *". I so far ended up with end-to-end recipe, but it's working with real gerrit. Example: https://build.chromium.org/p/tryserver.infra/builders/Try%20Recipe%20Mac/buil... I think I'll consider resurrecting this for faster standalone depot_tools tests. > > So... up to you, really. In my opinion, it's prudent to have test coverage to > prevent chrome infra changes from breaking due to incompatibilities with gerrit.
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/1820923002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1820923002/1
Message was sent while issue was closed.
Description was changed from ========== testing_support: fix Gerrit releases URL. R=szager@chromium.org,sergiyb@chromium.org BUG=579160 ========== to ========== testing_support: fix Gerrit releases URL. R=szager@chromium.org,sergiyb@chromium.org BUG=579160 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299408 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as http://src.chromium.org/viewvc/chrome?view=rev&revision=299408
Message was sent while issue was closed.
https://codereview.chromium.org/1820923002/diff/1/testing_support/gerrit-init.sh File testing_support/gerrit-init.sh (right): https://codereview.chromium.org/1820923002/diff/1/testing_support/gerrit-init... testing_support/gerrit-init.sh:80: # Disable using -rc versions. This is a temporary hack to avoid Maybe it's time to check whether this hack can be removed?
Message was sent while issue was closed.
On 2016/03/21 17:18:58, szager1 wrote: > https://codereview.chromium.org/1820923002/diff/1/testing_support/gerrit-init.sh > File testing_support/gerrit-init.sh (right): > > https://codereview.chromium.org/1820923002/diff/1/testing_support/gerrit-init... > testing_support/gerrit-init.sh:80: # Disable using -rc versions. This is a > temporary hack to avoid > Maybe it's time to check whether this hack can be removed? filed http://crbug.com/596905 - won't waste time, unless I actually start using gerrit. Otherwise, I'll wipe this whole thing out of depot_tools. |