From: Junio C Hamano <gitster@pobox.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t9604: Fix test for musl libc and new Debian
Date: Sat, 06 Apr 2024 05:11:30 -0700 [thread overview]
Message-ID: <xmqqsezylmh9.fsf@gitster.g> (raw)
In-Reply-To: <23a4298eababe54ca4b43d7b675b858605d20ec5.1712374021.git.congdanhqx@gmail.com> ("Đoàn Trần Công Danh"'s message of "Sat, 6 Apr 2024 10:29:10 +0700")
Đoàn Trần Công Danh <congdanhqx@gmail.com> writes:
> * Note that since our tests are pre-2007, I use the old rules in the timezone.
> * We can also use IANA notations, which I believe is better, but that mean we
> will depends on IANA db
I know of the ",start[/time],end[/time]" thing tucked after the
zonename, but haven't seen it used in real life. How confident are
you that it is widely supported? I do understand that you saw these
current tests do fail on some platforms, but we'd want to make sure
that we are not breaking other platforms by switching.
> -test_expect_success PERL 'check timestamps are UTC (TZ=CST6CDT)' '
> +test_expect_success PERL 'check timestamps are UTC (TZ=America/Chicago)' '
>
> - TZ=CST6CDT git cvsimport -p"-x" -C module-1 module &&
> + TZ=CST6CDT,M4.1.0,M10.5.0 \
> + git cvsimport -p"-x" -C module-1 module &&
> git cvsimport -p"-x" -C module-1 module &&
> (
> cd module-1 &&
A few things curious about this hunk.
- The test title says America/Chicago but that timezone is never
used. Would it make sense to actually use it for tests?
- If not, shouldn't we at least use the actual timezone we use for
tests?
- Do we really want to run cvsimport twice?
> @@ -38,9 +39,9 @@ test_expect_success PERL 'check timestamps with author-specific timezones' '
>
> cat >cvs-authors <<-EOF &&
> user1=User One <user1@domain.org>
> - user2=User Two <user2@domain.org> CST6CDT
> - user3=User Three <user3@domain.org> EST5EDT
> - user4=User Four <user4@domain.org> MST7MDT
> + user2=User Two <user2@domain.org> CST6CDT,M4.1.0,M10.5.0
> + user3=User Three <user3@domain.org> EST5EDT,M4.1.0,M10.5.0
> + user4=User Four <user4@domain.org> MST7MDT,M4.1.0,M10.5.0
> EOF
> git cvsimport -p"-x" -A cvs-authors -C module-2 module &&
> (
next prev parent reply other threads:[~2024-04-06 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 3:29 [PATCH] t9604: Fix test for musl libc and new Debian Đoàn Trần Công Danh
2024-04-06 12:11 ` Junio C Hamano [this message]
2024-04-07 1:38 ` Đoàn Trần Công Danh
2024-04-08 17:34 ` Junio C Hamano
2024-04-07 1:33 ` Jeff King
2024-04-07 1:45 ` Đoàn Trần Công Danh
2024-04-07 1:50 ` Đoàn Trần Công Danh
2024-04-10 3:28 ` [PATCH v2] " Đoàn Trần Công Danh
2024-04-10 3:29 ` Eric Sunshine
2024-04-10 3:35 ` Đoàn Trần Công Danh
2024-04-10 3:37 ` Eric Sunshine
2024-04-10 7:10 ` Đoàn Trần Công Danh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsezylmh9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=congdanhqx@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.