Only t/50mruby.t fails now:

spawning /<<PKGBUILDDIR>>/obj-hppa-linux-gnu/h2o... done
[INFO] raised RLIMIT_NOFILE to 524288
h2o server (pid:24270) is ready to serve requests
fetch-ocsp-response (using OpenSSL 3.0.11 19 Sep 2023 (Library: OpenSSL 3.0.11 
19 Sep 2023))
[WARNING] Certificate verification failed: unable to verify the first 
certificate

    #   Failed test 'receives index.js then /index.txt'
    #   at t/50mruby.t line 177.
    #                   '***** Statistics *****
    #
    # Request timing:
    #   responseEnd: the  time  when  last  byte of  response  was received
    #                relative to connectEnd
    #  requestStart: the time  just before  first byte  of request was sent
    #                relative  to connectEnd.   If  '*' is  shown, this  was
    #                pushed by server.
    #       process: responseEnd - requestStart
    #          code: HTTP status code
    #          size: number  of  bytes  received as  response  body without
    #                inflation.
    #           URI: request URI
    #
    # see http://www.w3.org/TR/resource-timing/#processing-model
    #
    # sorted by 'complete'
    #
    # id  responseEnd requestStart  process code size request path
    #  13    +30.00ms         +0us  30.00ms  200    6 /index.txt
    #   2    +30.00ms *   +30.00ms      0us  200   16 /index.js
    # '
    #     doesn't match 
'(?^si:\nid\s*responseEnd\s.*\s/index\.js\n.*\s/index\.txt)'
killing /<<PKGBUILDDIR>>/obj-hppa-linux-gnu/h2o... received SIGTERM, gracefully 
shutting down
failed to extract ocsp URI from examples/h2o/server.crt
killed (got 0)
    # Looks like you failed 1 test of 1.

#   Failed test 'server-push'
#   at t/50mruby.t line 178.

See the following logs:
https://buildd.debian.org/status/fetch.php?pkg=h2o&arch=alpha&ver=2.2.5%2Bdfsg2-8&stamp=1697823036&raw=0
https://buildd.debian.org/status/fetch.php?pkg=h2o&arch=hppa&ver=2.2.5%2Bdfsg2-8&stamp=1697911773&raw=0

Hopefully, this can be looked at.

Regards,
Dave Anglin

--
John David Anglin  dave.ang...@bell.net

Reply via email to