On Sat, 2020-12-26 at 15:59 +0100, Gianfranco Costamagna wrote:
> 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
On Saturday, December 26, 2020 8:35:08 A.M. CST Nicholas Guriev 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
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
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
Processing control commands:
> tag -1 pending
Bug #976037 [src:ms-gsl] ms-gsl's autopkg tests are broken by design
Added tag(s) pending.
--
976037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
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:
6 matches
Mail list logo
