On May 27, 2020, at 1:13 PM, Martin Mathieson via Wireshark-dev <wireshark-dev@xxxxxxxxxxxxx> wrote:
> Looking at the last cppcheck build on master ( https://buildbot.wireshark.org/wireshark-master/builders/Clang%20Code%20Analysis/builds/5214/steps/cppcheck/logs/stdio), it was done on the weekend but using an old revision of master.
>
> Looking at build 5214 (dated 24th May), it tests revision (9f3a335f459de8ac4eb5521f2c7e1820e95e2dfe) which was from 2nd March. Does something need to be done to make the next build move on?
That's not a cppcheck issue, it's an issue with the entire build - it's building an ancient commit, although it claims that there's only 1 commit pending.
https://buildbot.wireshark.org/wireshark-master/builders/Clang%20Code%20Analysis/builds/5214
says 1) it's commit 9f3a335f459de8ac4eb5521f2c7e1820e95e2dfe, which is
commit 9f3a335f459de8ac4eb5521f2c7e1820e95e2dfe
Author: Alexis La Goutte <alexis.lagoutte@xxxxxxxxx>
Date: Mon Mar 2 14:13:07 2020 +0100
QUIC: Add ACK_FREQUENCY Frame Type
From https://tools.ietf.org/html/draft-iyengar-quic-delayed-ack-00 and
https://github.com/quicwg/base-drafts/wiki/Temporary-IANA-Registry#quic-frame-types
and 2) that it started on May 24.
