On Tue, 27 Oct 2020 00:16:47 -0500 "Steve M. Robbins" <s...@debian.org> wrote: > Dear Maintainer, > > The autopkg tests need to be updated for the new googletest. There are failures such as > > /tmp/autopkgtest-lxc.u2mymoo7/downtmp/autopkgtest_tmp/unit/alphabet/cigar/../alphabet_test_template.hpp:86: Failure > Type parameterized test suite alphabet is defined via REGISTER_TYPED_TEST_SUITE_P, but never instantiated via INSTANTIATE_TYPED_TEST_SUITE_P. None of the test cases will run. > > Ideally, TYPED_TEST_P definitions should only ever be included as part of binaries that intend to use them. (As opposed to, for example, being placed in a library that may be linked in to get other utilities.)
Hello, googletest version 1.10.0.20201025 does not appear to be an official release of upstream: https://github.com/google/googletest/releases Why was a git snapshot with breaking changes packaged for Debian? I see some reference in upstream's README that they intend to follow: https://abseil.io/about/philosophy which includes the promise > If we need to refactor an API that you depend on, we will provide a tool that should be able to perform the refactoring for well-behaved code. But there is no refactoring tool related to this change. > We will periodically mark a tag as “supported” and branch it — if we discover security issues or major performance problems, we’ll update those branches. Our expectation is to do this every 6 months and support those branches for 2 years. No such branch has been made yet for googletest; I don't think they are expecting users to use the HEAD of the development branch yet. Seems that 1.10.0.20201025-1 needs to be rolled back, sorry. -- Michael R. Crusoe
signature.asc
Description: OpenPGP digital signature
