From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Test results for GNU HURD
Date: Wed, 25 Mar 2020 20:01:12 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2003252000200.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAH8yC8mn+c_v85eMTqLEZS1=OgetOKe9uX3MoPDmRZEyfENuTQ@mail.gmail.com>
Hi Jeffrey,
On Wed, 18 Mar 2020, Jeffrey Walton wrote:
> Hi Everyone,
>
> Here are test results for GNU HURD built from the 2.25.1 release
> tarball. HURD is the JAN 2020 image, and fully updated with apt-get.
>
> I may be missing something for testing.
Maybe you can re-run this test script with the `-i -v -x` options? That
will stop at the first failure, produce verbose output, and also trace the
commands as they are run.
Ciao,
Johannes
>
> *** t5562-http-backend-content-length.sh ***
> ok 1 - setup
> ok 2 - setup, compression related
> ok 3 - fetch plain
> ok 4 - fetch plain truncated
> ok 5 - fetch plain empty
> ok 6 - fetch gzipped
> ok 7 - fetch gzipped truncated
> ok 8 - fetch gzipped empty
> ok 9 - push plain
> ok 10 - push plain truncated
> ok 11 - push plain empty
> ok 12 - push gzipped
> not ok 13 - push gzipped truncated
> #
> # test_env HTTP_CONTENT_ENCODING="gzip" test_http_env receive
> push_body.gz.trunc &&
> # ! verify_http_result "200 OK"
> #
> not ok 14 - push gzipped empty
> #
> # test_env HTTP_CONTENT_ENCODING="gzip" test_http_env receive
> empty_body &&
> # ! verify_http_result "200 OK"
> #
> ok 15 - CONTENT_LENGTH overflow ssite_t
> ok 16 - empty CONTENT_LENGTH
> # failed 2 among 16 test(s)
> 1..16
> Makefile:56: recipe for target 't5562-http-backend-content-length.sh' failed
>
prev parent reply other threads:[~2020-03-25 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 23:44 Test results for GNU HURD Jeffrey Walton
2020-03-25 19:01 ` Johannes Schindelin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2003252000200.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).