Hello Nicholas, if you want to test newer compilers, you are free to do it, but maybe you can mark tests as flaky and exit 77 if they fail, so at least you can see failures by manually looking at logs...
This way you won't block migration to testing, you won't be RC buggy, but you will have the possibility to have test logs. what do you think? G. On Sat, 26 Dec 2020 17:35:08 +0300 Nicholas Guriev <nicho...@guriev.su> wrote: > I have rewritten auto-tests, so they do not longer require non-default > versions of compilers. Since the tests with GCC rely on the same version > of the compiler that built Google Test framework, I think preconditions > of Bug#972944 lose its relevance, and there is no need to rebuild the > googletest from sources (in /usr/src/googletest). > > Steve Robbins, am I right in my judgments? > > > On Sat, 2020-12-26 at 13:43 +0000, Nicholas Guriev wrote: > > Control: tag -1 pending > > > > Hello, > > > > Bug #976037 in ms-gsl reported by you has been fixed in the > > Git repository and is awaiting an upload. You can see the commit > > message below and you can check the diff of the fix at: > > > > https://salsa.debian.org/debian/ms-gsl/-/commit/66a9aa1dea09f4619e2ced31c8f277fda0eaa9b9 > > > > ------------------------------------------------------------------------ > > Run autopkgtests only against default GCC and Clang > > > > * At Matthias Klose's request, removed auto-tests with fixed versions of > > GCC > > or Clang. Instead, use default compilers. > > * Rewritten the tests so that they include system-wide installed GSL > > headers. > > > > Closes: #976037 > > ------------------------------------------------------------------------ > > > > (this message was generated automatically) >
