1674366 - Update to neqo 0.4.14

Status: RESOLVED FIXED

(Core :: Networking: HTTP, task, P2)

Comment 1

[Dragana Damjanovic [:dragana]]

Attachment: Neqo version 0.4.14

Comment 2

[Dragana Damjanovic [:dragana]]

Attachment: Adapt to the neqo API changes

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/7c1e47fbd4fe
Neqo version 0.4.14 r=necko-reviewers,valentin
https://hg.mozilla.org/integration/autoland/rev/728566a74fd5
Adapt to the neqo API changes r=necko-reviewers,valentin

Comment 4

[Dorel Luca [:dluca]]

https://hg.mozilla.org/mozilla-central/rev/7c1e47fbd4fe
https://hg.mozilla.org/mozilla-central/rev/728566a74fd5

Comment 5

[Alexandru Ionescu (needinfo me) [:alexandrui]]

Hi dragana. We have the performance regression below and your patch seems to be the only one that might cause a regression. Does that make sense for you?

== Change summary for alert #27601 (as of Wed, 11 Nov 2020 13:38:20 GMT) ==

Regressions:

Ratio	Suite	Test	Platform	Options	Absolute values (old vs new)
8%	imdb	SpeedIndex	linux64-shippable-qr	cold webrender	960.94 -> 1,038.58
8%	imdb	SpeedIndex	linux64-shippable	cold	956.16 -> 1,031.67

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=27601

Comment 6

[Dragana Damjanovic [:dragana]]

I do not see how this patch can cause the regression. The code is never run it is behind a pref.
Is there any other possible change log that could cause this?