El 21/3/23 a las 19:57, Chris Hofstaedtler escribió:
it seems like its not 100% reproducible (in my builds at least).
Hello. I can reproduce the FTBFS failure in a consistent way (i.e. not randomly but always) on three different kind of machines: Self-hosted VMs using kvm, VMs from GCP, and VMs from Hetzner. If you (or anybody else interested) want to debug this and it only fails randomly for you, please contact me privately and I can provide ssh access to a test machine where it happens always. This is my build history with all the machines combined: Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220430T092608.165Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220503T213948.786Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220509T175008.611Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220509T181241.653Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221210T052645.088Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221211T062519.570Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221212T002906.924Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221212T004404.360Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230310T080600.446Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230310T081557.903Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230311T113541.485Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230311T215111.404Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160532.877Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160534.994Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160639.774Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160726.134Z One of the things which happened between 20221212 and 20230310 is that I started to use bookworm as the host OS for my VMs, so it could be the kernel. Thanks.
