git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: RE: Git 2.16.0-rc2 Test Summary on NonStop
Date: Sat, 13 Jan 2018 14:30:40 -0500	[thread overview]
Message-ID: <004701d38ca5$024dec30$06e9c490$@nexbridge.com> (raw)
In-Reply-To: <003701d38c99$65657830$30306890$@nexbridge.com>

On January 13, 2018 1:08 PM, I wrote:
> Here’s where things are. This is probably the best git release so far
(ever).
> After applying a4cdf02, I had 6 total breakages. 3 existing, 3 new.
> Many reduced. The test took about 24 hours to run on platform, which is
> about 2 hours shorter than 2.13.5.
> 
> t1308-config-set.sh (2 already discussed and expecting a fix, both appear
to
> be issues in the test script, not code) t1404-update-ref-errors.sh # 52 –
> reported but not discussed:
>    not ok 52 - delete fails cleanly if packed-refs file is locked.
>      The lock detection worked, but the test assumed the detection would
> occur in a different spot.
> t9001-send-email.sh (2 have existed for 2 years. 1 is new. We have not
used
> send-email on platform to this point).
>    not ok 31 - reject long lines
>      This is a new fail since 2.8.5
>   not ok 106 - sendemail.transferencoding=7bit fails on 8bit data
>      Still to be investigated. This may be a tooling issue on Platform.
>   not ok 107 - --transfer-encoding overrides sendemail.transferEncoding
>      Still to be investigated. This may be a tooling issue on Platform.

I missed one:
not ok 134 - --dump-aliases must be used alone
#
#               test_must_fail git send-email --dump-aliases
--to=janice@example
.com -1 refs/heads/accounting
#

This one has been around at least since 2.5.6.


      reply	other threads:[~2018-01-13 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-13 18:07 Git 2.16.0-rc2 Test Summary on NonStop Randall S. Becker
2018-01-13 19:30 ` Randall S. Becker [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='004701d38ca5$024dec30$06e9c490$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    /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).