Bump googletest for compatibility with clang-cl#13161
Bump googletest for compatibility with clang-cl#13161mattklein123 merged 4 commits intoenvoyproxy:masterfrom greenhouse-org:update-googletest
Conversation
- Submitting this independently to determine that this revision of googletest does not introduce breakage on any toolchain - See issue: google/googletest#2490 Co-authored-by: Sunjay Bhatia <sunjayb@vmware.com> Co-authored-by: William A Rowe Jr <wrowe@vmware.com> Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com> Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
|
cc @wrowe |
|
@htuch This is the googletest bump required for clang-cl on Windows. Let's see how it pans out on all existing CI pipelines, then please expedite merging to master on success. |
Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
| sha256 = "9dc9157a9a1551ec7a7e43daea9a694a0bb5fb8bec81235d8a1e6ef64c716dcb", | ||
| strip_prefix = "googletest-release-{version}", | ||
| urls = ["https://github.com/google/googletest/archive/release-{version}.tar.gz"], | ||
| # 2020-09-10 |
There was a problem hiding this comment.
Thanks for the update. Please include an explanation as per policy, see https://github.com/envoyproxy/envoy/blob/master/DEPENDENCY_POLICY.md
Versions should prefer release versions over master branch GitHub SHA tarballs. A comment is necessary if the latter is used. This comment should contain the reason that a non-release version is being used and the YYYY-MM-DD when the last update was performed.
There was a problem hiding this comment.
Indeed, I had misunderstood the exception r.e. CPE's and test-only elements of the build, but hope you find the new message appropriate. Not really certain if there will be a 1.11 "release" given the general google philosophy of consuming the dev branch, and with respect to our test architecture, any of their bleed efforts to identify defects should be picked up fairly frequently (although probably not daily.)
|
As this is a blocking issue for other PR's we would ask @envoyproxy/senior-maintainers if anyone has cycles to give this a green light and pull it? |
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
Signed-off-by: William A Rowe Jr <wrowe@vmware.com>
|
/retest |
|
Retrying Azure Pipelines, to retry CircleCI checks, use |
Commit Message: Bump googletest
For compatibility with Windows clang-cl
Additional Description: Submitting this independently to determine that this revision of googletest does not introduce breakage on any toolchain. See issue: google/googletest#2490. Step to address #11974
Risk Level: Low
Testing: Compiles with Windows clang-cl
Docs Changes: N/A
Release Notes: N/A