Aggressive transport sender behaviour inconsistencies due to version upgrade

When running ./ns3 run aqm-eval-suite-runner -- --name=AggressiveTransportSender --AggressiveTcp=TcpHighSpeed the queue delay becomes 0 after the first spike where running on the old version gives the sawtooth pattern. I've also tried this on a bare bone version of the evaluation module that was rebased on latest ns3 without any modifications.