In TestHybridPool attempt to prime to the windows root pool before
the real test actually happens. This is a bit of a band-aid, with
a better long term solution discussed in #52108.
Reviewed-by: Bryan Mills <email@example.com>
TryBot-Result: Gopher Robot <firstname.lastname@example.org>
Run-TryBot: Roland Shoemaker <email@example.com>
I think the above failures may have been due to a misconfiguration of the badssl.com service itself, although it does seem strange to me that it only failed on Windows.
I wonder if the Windows root store ended up pulling in one of the badssl.com certificates but not the others, causing the error to be reported from the wrong certificate? Or maybe the badssl.com service itself was misconfigured for a while...