On Sun, Feb 25, 2024 at 09:00:55PM +0100, Patrice Dumas wrote:
> On Sun, Feb 25, 2024 at 07:43:42PM +, Gavin Smith wrote:
> > It appears that there was no effort made to reset the counters at all.
> > If a parser run finished with one of the counters active, it would
> > remain active for the
On Sun, Feb 25, 2024 at 07:43:42PM +, Gavin Smith wrote:
> It appears that there was no effort made to reset the counters at all.
> If a parser run finished with one of the counters active, it would
> remain active for the next run.
Shouldn't there be an error message for the counters that
On Sun, Feb 25, 2024 at 07:01:22PM +, Gavin Smith wrote:
> So it appears there is a problem with the counter not being reset properly
> before the test runs, or sometime early on in the run.
>
> I'll try and do more investigation.
It appears that there was no effort made to reset the
On Sun, Feb 25, 2024 at 04:47:46PM +, Gavin Smith wrote:
> I occasionally get test failures in the
> "perl -w t/03coverage_braces.t definfoenclose_texinfo_commands" test,
> but cannot usually repeat it reliably. I suspect some issue with memory
> corruption or issue with uninitialised memory,
