From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net] selftests: mptcp: drop nanoseconds width specifier
Date: Fri, 15 May 2026 06:15:04 +0200 [thread overview]
Message-ID: <596161e3-031e-47e1-a6ad-a9bf96abb119@kernel.org> (raw)
In-Reply-To: <822ad467-2d97-4c2f-8e5b-78be0bd0acf2@kernel.org>
On 15/05/2026 05:59, Matthieu Baerts wrote:
> Hello,
>
> On 15/05/2026 04:11, Matthieu Baerts (NGI0) wrote:
>> Using the format specifier +%s%3N with GNU date is honoured, and only
>> prints 3 digits of the nanoseconds portion of the seconds since epoch,
>> which corresponds to the milliseconds.
>>
>> The uutils implementation of date currently does not honour this, and
>> always prints all 9 digits. This is a known issue [1], but can be worked
>> around by adapting this test to use nanoseconds instead of microseconds,
>> and then divide it by 1e6.
>>
>> This fix is similar to what has been done on systemd side [2].
>
> I suggest applying this patch, and sending to netdev-net, not to block
> those using uutils, e.g. on Ubuntu 26.04.
>
> I will apply a small change, see below.
Now in our tree:
New patches for t/upstream-net and t/upstream:
- ddfbd0a8f455: selftests: mptcp: drop nanoseconds width specifier
- Results: abcff95a440d..c6403a142d47 (export-net)
- Results: 564a2979a856..17d8ed7a3a1c (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/91d16c37e15ffff4ea145b5b7c897f2f4e5cfd3d/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/bae8b1e40c2d814e5d571dfa0885a59722911bb6/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-05-15 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 2:11 [PATCH mptcp-net] selftests: mptcp: drop nanoseconds width specifier Matthieu Baerts (NGI0)
2026-05-15 3:19 ` MPTCP CI
2026-05-15 3:59 ` Matthieu Baerts
2026-05-15 4:15 ` Matthieu Baerts [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=596161e3-031e-47e1-a6ad-a9bf96abb119@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/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.