From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: git@vger.kernel.org
Cc: Chris Torek <chris.torek@gmail.com>
Subject: t4068 test failure with -fsanitize=address
Date: Tue, 7 Jul 2020 23:54:36 +0000 [thread overview]
Message-ID: <20200707235436.GH9782@camp.crustytoothpaste.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
I was kicking off a build on a cloud instance for the final series of my
SHA-256 work and I noticed that t4068 fails with -fsanitize=address
using Debian's GCC 9.3.0-14 (the version in unstable). It has failed
since the test was introduced and currently fails on the latest HEAD.
I haven't had time to look at it, but I thought I'd pass the information
on so we can get it fixed before the release. I'll take a look if
nobody else gets to it first, but it may be a few days.
Reproduction steps:
printf 'DEVELOPER=1\nDC_SHA1=1\nBLK_SHA256=1\nSANITIZE=address\n' >config.mak
make -j6 all && (cd t && ./t4068-*.sh --verbose)
Output with --verbose:
expecting success of 4068.4 'diff with no merge bases':
test_must_fail git diff br2...br3 >tmp 2>err &&
test_i18ngrep "fatal: br2...br3: no merge base" err
test_must_fail: died by signal 6: git diff br2...br3
not ok 4 - diff with no merge bases
#
# test_must_fail git diff br2...br3 >tmp 2>err &&
# test_i18ngrep "fatal: br2...br3: no merge base" err
#
--
brian m. carlson: Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next reply other threads:[~2020-07-07 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 23:54 brian m. carlson [this message]
2020-07-08 4:38 ` [PATCH] diff: check for merge bases before assigning sym->base Jeff King
2020-07-08 17:05 ` Chris Torek
2020-07-09 23:02 ` Jeff King
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=20200707235436.GH9782@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=chris.torek@gmail.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).