|
|
Created:
3 years, 8 months ago by Robert Ogden Modified:
3 years, 7 months ago CC:
chromium-reviews, tbansal+watch-data-reduction-proxy_chromium.org Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionAdd Chrome version check decorators
Uses lazy loading to only get the version when needed, and uses a global
variable (yuck) to store it for all future test runs.
BUG=712688
Review-Url: https://codereview.chromium.org/2826733002
Cr-Commit-Position: refs/heads/master@{#466390}
Committed: https://chromium.googlesource.com/chromium/src/+/9378ff37d394367870aec12cef1c9ee42633fe39
Patch Set 1 #
Total comments: 2
Messages
Total messages: 21 (9 generated)
robertogden@chromium.org changed reviewers: + ryansturm@chromium.org
Ryan, please take a look. Thanks!
ryansturm@chromium.org changed reviewers: + bengr@chromium.org
Adding bengr. I still think storing a frozen version of the integration test code once it hits stable is the better option, but I defer to Ben on this one.
On 2017/04/18 18:53:14, Ryan Sturm wrote: > Adding bengr. I still think storing a frozen version of the integration test > code once it hits stable is the better option, but I defer to Ben on this one. Yeah, I agree with Ryan. The caveat is that decorators would be a lot easier for two cases: 1) testing archived releases, because you wouldn't have to fetch old source as well. 2) documenting the evolution of expected behavior in one location. Robert, I'm fine either way. Discuss with Richard. If you can come to a workable solution for (1) without this CL, then I'd forego the CL.
On 2017/04/20 00:46:14, bengr wrote: > On 2017/04/18 18:53:14, Ryan Sturm wrote: > > Adding bengr. I still think storing a frozen version of the integration test > > code once it hits stable is the better option, but I defer to Ben on this one. > > Yeah, I agree with Ryan. The caveat is that decorators would be a lot easier for > two cases: > 1) testing archived releases, because you wouldn't have to fetch old source as > well. > 2) documenting the evolution of expected behavior in one location. > > Robert, I'm fine either way. Discuss with Richard. If you can come to a workable > solution for (1) without this CL, then I'd forego the CL. I'd rather go with the decorator option. There are several scenarios where we want changes to propagate back, like a server change that requires updates to the tests, new tests that are backwards compatible, and changes to the test infrastructure (like a new device / platform). It would be easier to have ToT be the source of truth for all that, than trying to maintain k branches of stable.
lgtm if this is the best way to do it WRT infrastructure.
The CQ bit was checked by robertogden@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: win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...) win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...) win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by robertogden@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: win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
The CQ bit was checked by robertogden@chromium.org
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": 1492797534247230, "parent_rev": "9264f7911c85f9bcb3c357b7f2989a70a0c3aef8", "commit_rev": "9378ff37d394367870aec12cef1c9ee42633fe39"}
Message was sent while issue was closed.
Description was changed from ========== Add Chrome version check decorators Uses lazy loading to only get the version when needed, and uses a global variable (yuck) to store it for all future test runs. BUG=712688 ========== to ========== Add Chrome version check decorators Uses lazy loading to only get the version when needed, and uses a global variable (yuck) to store it for all future test runs. BUG=712688 Review-Url: https://codereview.chromium.org/2826733002 Cr-Commit-Position: refs/heads/master@{#466390} Committed: https://chromium.googlesource.com/chromium/src/+/9378ff37d394367870aec12cef1c... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/9378ff37d394367870aec12cef1c...
Message was sent while issue was closed.
Hmm, fwiw, I never published these nits. https://codereview.chromium.org/2826733002/diff/1/tools/chrome_proxy/webdrive... File tools/chrome_proxy/webdriver/decorator_smoke.py (right): https://codereview.chromium.org/2826733002/diff/1/tools/chrome_proxy/webdrive... tools/chrome_proxy/webdriver/decorator_smoke.py:24: @ChromeVersionBeforeM(0) Hmm. Maybe call this ChromeMaximumMilestone or ChromeMaxMilestone? https://codereview.chromium.org/2826733002/diff/1/tools/chrome_proxy/webdrive... File tools/chrome_proxy/webdriver/decorators.py (right): https://codereview.chromium.org/2826733002/diff/1/tools/chrome_proxy/webdrive... tools/chrome_proxy/webdriver/decorators.py:83: t.LoadURL('http://check.googlezip.net/connect') Maybe use a standard gen_204 page, or just scrape chrome://version? |