From: Martin Wilck <martin.wilck@suse.com>
To: Luis Chamberlain <mcgrof@kernel.org>, shinichiro.kawasaki@wdc.com
Cc: linux-block@vger.kernel.org, patches@lists.linux.dev,
gost.dev@samsung.com
Subject: Re: [PATCH blktests] nvme/053: provide time extension alternative
Date: Wed, 08 Jan 2025 21:37:07 +0100 [thread overview]
Message-ID: <f693d9e8e0ece410ea6a8d1cfc26945286178231.camel@suse.com> (raw)
In-Reply-To: <20241218111340.3912034-1-mcgrof@kernel.org>
On Wed, 2024-12-18 at 03:13 -0800, Luis Chamberlain wrote:
> I get this failure when I run this test:
>
> awk: ...rescan.awk:2: warning: The time extension is obsolete.
> Use the timex extension from gawkextlib
>
> I can't find this extension either, so just use systime() and
> use system(sleep) for the sleep command.
While I'm ok with Shinshiro's propsal for working around this issue, I
wonder which gawk version you are using? In the history of gawk, I can
see that the deprecation of the "time" extension (gawk 5.2.0) was taken
back in gawk 5.2.2:
c3c6419 ("Make the time extension deprecated.")
6e195e4 ("Undeprecate the time extension, add strptime, update tests
and doc.")
The NEWS file says "The time extension is no longer deprecated. The
strptime() function from gawkextlib's timex extension has been added to
it."
Regards,
Martin
prev parent reply other threads:[~2025-01-08 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 11:13 [PATCH blktests] nvme/053: provide time extension alternative Luis Chamberlain
2024-12-20 11:37 ` Shinichiro Kawasaki
2025-01-04 4:05 ` Luis Chamberlain
2025-01-08 20:12 ` Martin Wilck
2025-01-16 7:17 ` Shinichiro Kawasaki
2025-01-08 20:37 ` Martin Wilck [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=f693d9e8e0ece410ea6a8d1cfc26945286178231.camel@suse.com \
--to=martin.wilck@suse.com \
--cc=gost.dev@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=patches@lists.linux.dev \
--cc=shinichiro.kawasaki@wdc.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox