zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Re: Test release: 5.8.1.2-test
Date: Tue, 12 Apr 2022 20:40:38 +0200	[thread overview]
Message-ID: <20220412184037.zluwiilc5ol45is3@sym.noone.org> (raw)
In-Reply-To: <20220412175512.2p6yyi3t3awb6nkm@sym.noone.org>

Hi again,

On Tue, Apr 12, 2022 at 07:55:14PM +0200, Axel Beckert wrote:
> 875 run-testsuite-static FAIL stderr: (eval):7: permission denied: /file
[…]
> The question is how to fix this properly. My suggestion would be to
> move "tst_dir=V14.tmp" as well as "mkdir -p -- $tst_dir" out of the
> conditional, something along these lines:
> 
> diff --git a/Test/V14system.ztst b/Test/V14system.ztst
> index 100daab08..1e683b5b9 100644
> --- a/Test/V14system.ztst
> +++ b/Test/V14system.ztst
> @@ -2,10 +2,9 @@
>  
>  %prep
>  
> -  if zmodload -s zsh/system && zmodload -s zsh/zselect; then
> -    tst_dir=V14.tmp
> -    mkdir -p -- $tst_dir
> -  else
> +  tst_dir=V14.tmp
> +  mkdir -p -- $tst_dir
> +  if ! ( zmodload -s zsh/system && zmodload -s zsh/zselect ); then
>      ZTST_unimplemented='the zsh/system and zsh/zselect modules are not available'
>    fi
>    : > $tst_dir/file # File on which to acquire flock.

Nope, that test now fails with with non-static zsh as follows:

../../Test/V14system.ztst: starting.
Running test: zsystem flock valid time arguments
Test ../../Test/V14system.ztst failed: bad status 127, expected 0 from:
  (
    zsystem flock -t 0 -i 0.000001 $tst_dir/file    &&
    zsystem flock -t 0.1 -i 0.000001 $tst_dir/file  &&
    zsystem flock -t 0.1 -i 0.0000001 $tst_dir/file &&
    zsystem flock -t 1 -i 0.000001 $tst_dir/file
  )
Error output:
(eval):2: command not found: zsystem
Was testing: zsystem flock valid time arguments
../../Test/V14system.ztst: test failed.

So I currently have no idea how to fix that properly.

		Kind regards, Axel
-- 
PGP: 2FF9CD59612616B5      /~\  Plain Text Ribbon Campaign, http://arc.pasp.de/
Mail: abe@deuxchevaux.org  \ /  Say No to HTML in E-Mail and Usenet
Mail+Jabber: abe@noone.org  X
https://axel.beckert.ch/   / \  I love long mails: https://email.is-not-s.ms/


  reply	other threads:[~2022-04-12 18:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 20:07 dana
2022-04-09 20:18 ` Bart Schaefer
2022-04-10 20:07 ` Peter Stephenson
2022-04-12  9:16   ` Peter Stephenson
2022-04-10 20:21 ` Luna Jernberg
2022-04-11  0:32 ` Axel Beckert
2022-04-11  8:30   ` Axel Beckert
2022-04-11 19:54     ` Bart Schaefer
2022-04-12  2:39       ` Jun T
2022-04-12  3:58         ` Bart Schaefer
2022-04-12  6:30           ` Jun T
2022-04-12  7:17             ` Jun T
2022-04-12  9:05             ` Axel Beckert
2022-04-12 17:55               ` [PATCH] " Axel Beckert
2022-04-12 18:40                 ` Axel Beckert [this message]
2022-04-13  1:17                   ` [PATCH] " Jun T
2022-04-13  9:34                     ` Axel Beckert
2022-04-11 10:44 ` Kamil Dudka

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=20220412184037.zluwiilc5ol45is3@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --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).