git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Han-Wen Nienhuys <hanwen@google.com>
Subject: [PATCH 0/4] deterministic commit timestamps in tests
Date: Thu, 9 Jul 2020 16:33:36 -0400	[thread overview]
Message-ID: <20200709203336.GA2748777@coredump.intra.peff.net> (raw)

Most tests use test_tick or test_commit to get deterministic timestamps
in commits. Some don't because they don't care about the timestamps. But
they can still be annoying to debug, since the output changes from run
to run.

This series sets a default timestamp for those scripts, in a way that
doesn't interfere with anybody using test_tick. The change is in the
final commit. The others are preparatory to deal with fallout in the
test suite. Normally fallout would give me pause about whether this is a
good idea, but a) there's not much of it and b) I think it helped shake
out questionable assumptions in those tests.

This a replacement for the patches being discussed in:

  https://lore.kernel.org/git/pull.816.git.git.1594149804313.gitgitgadget@gmail.com/

It looks like Junio already picked up one of the fixes as
jk/t6000-timestamp-fix. The first patch here is identical (so we can
either drop that branch, or drop the first patch from this series and
apply on top).

  [1/4]: t6000: use test_tick consistently
  [2/4]: t9700: loosen ident timezone regex
  [3/4]: t5539: make timestamp requirements more explicit
  [4/4]: test-lib: set deterministic default author/committer date

 t/t5539-fetch-http-shallow.sh | 4 +++-
 t/t6000-rev-list-misc.sh      | 7 +++++--
 t/t9700/test.pl               | 6 +++---
 t/test-lib.sh                 | 3 +++
 4 files changed, 14 insertions(+), 6 deletions(-)

-Peff

             reply	other threads:[~2020-07-09 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 20:33 Jeff King [this message]
2020-07-09 20:34 ` [PATCH 1/4] t6000: use test_tick consistently Jeff King
2020-07-09 20:35 ` [PATCH 2/4] t9700: loosen ident timezone regex Jeff King
2020-07-09 20:39 ` [PATCH 3/4] t5539: make timestamp requirements more explicit Jeff King
2020-07-09 20:42 ` [PATCH 4/4] test-lib: set deterministic default author/committer date Jeff King
2020-07-10 22:02 ` [PATCH 0/4] deterministic commit timestamps in tests Junio C Hamano
2020-07-14 12:31   ` Jeff King
2020-07-14 12:33     ` Jeff King
2020-07-14 21:47       ` Eric Wong
2020-07-15  7:42         ` Jeff King
2020-07-15 14:50           ` Junio C Hamano
2020-07-15 15:04             ` Junio C Hamano
2020-07-16 10:43               ` 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=20200709203336.GA2748777@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hanwen@google.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).