сб, 21 нояб. 2020 г. в 22:55, Tim Düsterhus <[email protected]>:
> Ilya, > > Am 21.11.20 um 18:51 schrieb Илья Шипицин: > >>> there's single job configuration without strict debug > >>> https://github.com/haproxy/haproxy/blob/master/.travis.yml#L66 > >>> > >>> I think there are couple of options available > >>> > >>> 1) add similar job definition to github actions > >>> > >>> 2) make DEBUG_STRICT=1 default and only option > >> > >> This is what I did. Anything crashing by using DEBUG_STRICT is a bug by > >> > > > > my english is not perfect, I know :) > > > > look. > > > > DEBUG_STRICT is enabled by default > > https://github.com/haproxy/haproxy/blob/master/.travis.yml#L17 > > > > but is is suppressed for a single jon definition > > https://github.com/haproxy/haproxy/blob/master/.travis.yml#L66 > > > > the idea behind it was "we'd better to test in strict mode, but who > knows, > > if there's something wrong without strict debug, we should also know" > > > > my suggestion is to mimic previous behaviour ... or disable empty > > DEBUG_STRICT at all maybe > > > > By "disable empty DEBUG_STRICT at all" you mean completely removing the > build option? I understood the "default and only option" as "in CI only". > yep. in build options (Makefile, source code, everywhere). so, we run ERR=1 for a year or so. everything is good. why not to make life simple and remove all other values of ERR in favour of ERR=1 ? > > Willy also requested to mimic the previous behavior, thus I'll just add > that build as a scheduled build when I get around to it. > > Best regards > Tim Düsterhus >
