zsh-workers
 help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: C02 '-N cond' test (was: [zsh:code] New commit [e89060] by dana)
Date: Fri, 14 Feb 2020 18:34:50 -0600	[thread overview]
Message-ID: <7C1CC946-C125-46F0-BBA5-E6377851DD0C@dana.is> (raw)
In-Reply-To: <20200214223449.656ee1a3@tarpaulin.shahaf.local2>

On 14 Feb 2020, at 16:34, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> Thanks.  It worked on my machine, probably because I link modules
> statically.

np, sorry i didn't notice it before now.

Semi-related: I can't remember if this always happens or it's intermittent,
but the '-N cond' test in C02 fails for me as well, apparently because APFS
defaults to (the equivalent of) noatime.

I found workers/38355, but both the thread and the test itself are a little
hard for me to follow. Could we not do something like this?

  touch $newnewnew
  sleep 2
  if ! zmodload -F zsh/stat b:zstat 2> /dev/null; then
    ZTST_skip='[[ -N file ]] not tested; zsh/stat not available'
  elif ! touch -a $unmodified 2> /dev/null; then
    ZTST_skip='[[ -N file ]] not tested; touch failed'
  elif [[ "$(zstat +atime $unmodified)" == "$(zstat +mtime $unmodified)" ]]; then
    ZTST_skip='[[ -N file ]] not supported on this file system'
  else
    [[ -N $newnewnew && ! -N $unmodified ]]
  fi

PS: I'm not worried about this for 5.8, since i've seen it before; just
mentioning while it's on my mind

dana


  reply	other threads:[~2020-02-15  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e02941db80101cde47889c9bf7906fea0b0e85ee.code@zsh.p.sourceforge.net>
2020-02-14 22:34 ` [zsh:code] New commit [e89060] by dana Daniel Shahaf
2020-02-15  0:34   ` dana [this message]
2020-02-18 22:20     ` C02 '-N cond' test (was: [zsh:code] New commit [e89060] by dana) dana

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=7C1CC946-C125-46F0-BBA5-E6377851DD0C@dana.is \
    --to=dana@dana.is \
    --cc=zsh-workers@zsh.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://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).