Hi! On Thu, Jan 21, 2021 at 02:55:08PM +0100, Florian Westphal wrote: > The tests fail because json printing omits a burst of 5 and > the parser treats that as 'burst 0'. While this patch is correct in that it aligns json and bison parser behaviours, I think omitting burst value in JSON output is a bug by itself: We don't care about output length and users are supposed to parse (and thus filter) the information anyway, so there's no gain from omitting such info. I'll address this in a separate patch, though. Thanks, Phil
