Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)

2023-03-21 Thread Santiago Vila
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

Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)

2023-03-21 Thread Anton Gladky
Hi Chris, thanks for your work! Please go ahead and upload without a delay. Please push your changes to git and tag it. Thanks and regards Anton Am Di., 21. März 2023 um 19:57 Uhr schrieb Chris Hofstaedtler < z...@debian.org>: > Hi, > > I will upload a change disabling the failing test to

Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)

2023-03-21 Thread Chris Hofstaedtler
Hi, I will upload a change disabling the failing test to DELAYED/7. Please let me know if I should cancel it. Debdiff attached. The failing mruby test might or might not point to a real problem, it seems like its not 100% reproducible (in my builds at least). I want src:h2o / libh2o to stay in