From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: Stefan Beller <sbeller@google.com>
Subject: [RFD PATCH 0/2] How to migrate our test infrastructure away from sha1
Date: Fri, 28 Jul 2017 10:18:15 -0700 [thread overview]
Message-ID: <20170728171817.21458-1-sbeller@google.com> (raw)
Brian got the ball rolling with his object-id patches
to fixup the code base, but we also need to discuss how
we approach our test infrastructure eventually.
C.f.:
* jb/t8008-cleanup (2017-07-26) 1 commit
- t8008: rely on rev-parse'd HEAD instead of sha1 value
* sb/t4005-modernize (Remove hard coded sha1 values.)
This presents an alternative approach in the second patch,
which just marks tests as "SHA1" required instead of making
the test hash-agnostic.
The first patch is just an aid to show which tests need
addressing, although there are some false positives (i.e.
the test fails for other reasons than the hash dependency,
such as corruption of data.)
Stefan
Stefan Beller (2):
alter hash function: expose test dependencies on sha1
t6500: mark tests as SHA1 reliant
sha1dc/sha1.c | 2 +-
t/t6500-gc.sh | 6 +++---
t/test-lib.sh | 4 ++++
3 files changed, 8 insertions(+), 4 deletions(-)
--
2.14.0.rc0.3.g6c2e499285
next reply other threads:[~2017-07-28 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 17:18 Stefan Beller [this message]
2017-07-28 17:18 ` [PATCH 1/2] alter hash function: expose test dependencies on sha1 Stefan Beller
2017-07-28 21:52 ` Junio C Hamano
2017-07-28 17:18 ` [PATCH 2/2] t6500: mark tests as SHA1 reliant Stefan Beller
2017-07-28 17:59 ` Junio C Hamano
2017-07-28 21:43 ` Stefan Beller
2017-07-28 22:14 ` Junio C Hamano
2017-07-29 17:58 ` brian m. carlson
2017-07-30 21:21 ` Junio C Hamano
2017-07-30 23:00 ` brian m. carlson
2017-07-30 23:24 ` brian m. carlson
2017-07-31 20:17 ` Ævar Arnfjörð Bjarmason
2017-07-31 20:30 ` Stefan Beller
2017-07-31 20:26 ` Stefan Beller
2017-07-31 23:54 ` brian m. carlson
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=20170728171817.21458-1-sbeller@google.com \
--to=sbeller@google.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).