zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: PATCH: Re: Running tests without installing Zsh
Date: Fri, 3 Mar 2000 17:37:06 +0000	[thread overview]
Message-ID: <1000303173706.ZM20761@candle.brasslantern.com> (raw)
In-Reply-To: <000301bf8505$bd6c8640$21c9ca95@mow.siemens.ru>

On Mar 3,  2:43pm, Andrej Borsenkow wrote:
} Subject: Running tests without installing Zsh
}
} If Zsh is compiled with dynamic loading, it is near to impossible to run
} tests without installing Zsh (at least, Zsh modules and, probably,
} functions).

I'd been noticing that.  The completion test in particular requires both
functions and dynamic loading; zregexparse needs modules.  Otherwise the
tests have been of purely builtin functionality.

Maybe we could encode this in the test-numbering scheme somehow ...

} Even setting module_path to $srcdir/Src/*(/) does not help,
} because Zsh loads modules as zsh/<module> - and we do not have zsh
} subdirectories in this case.

We can deal with that, I think.

} Of course, if any test runs as interactive, it will pick up wrong module
} anyway as we cannot override module_path at Zsh startup.

That's fixable, too.  The one thing we can't fix is that modules may be
autoloaded if the system has an /etc/zshenv file.  

} Is any module loaded at non-interactive shell startup?

Only the built-in pseudo-modules, unless /etc/zshenv causes one to be
loaded.

Here's a patch.  BTW, I noticed a number of inconsequential typos in
comptest, but didn't bother to fix any of them.  It would be nice if
comptest displayed some sort of progress indication, the way the traps
tests do; at one point while trying the changes below one of the zsh
running inside zpty exited prematurely, and the result was that comptest
locked up and had to be killed.  I didn't know how long to wait before
giving up on it.

Index: Test/53completion.ztst
===================================================================
@@ -3,6 +3,7 @@
 %prep
   zmodload -i zsh/zpty
 
+  export ZTST_testdir ZTST_srcdir
   comptest () { $ZTST_testdir/../Src/zsh -f $ZTST_srcdir/comptest -z $ZTST_testdir/../Src/zsh -d $ZTST_testdir/compdump.tmp "$@" }
 
   mkdir comp.tmp
Index: Test/Makefile.in
===================================================================
@@ -41,9 +41,14 @@
 # ========== DEPENDENCIES FOR TESTING ==========
 
 check test:
+	if test -n "$(DLLD)"; then \
+	  cd $(dir_top) && \
+	  $(MAKE) MODDIR=`pwd`/$(subdir)/Modules install.modules > /dev/null; \
+	fi
 	for f in $(sdir)/*.ztst; do \
-	  ../Src/zsh -f $(sdir)/ztst.zsh $$f; \
+	  $(dir_top)/Src/zsh -f $(sdir)/ztst.zsh $$f; \
 	done
+	rm -rf Modules
 
 # ========== DEPENDENCIES FOR CLEANUP ==========
 
Index: Test/comptest
===================================================================
@@ -1,8 +1,12 @@
 #!/usr/local/bin/zsh -f
 
+[[ -d $ZTST_testdir/Modules/zsh ]] && module_path=( $ZTST_testdir/Modules )
+
 zmodload -i zsh/zpty
 setopt extendedglob
 
+fpath=( ${ZTST_srcdir:h}/(Completion|Functions)/*~*/CVS(/) )
+
 debug=
 dump=(-D)
 code=
@@ -24,6 +28,8 @@
 tmp=/tmp/comptest.$$
 
 cat <<End >$tmp
+module_path=( $module_path )
+fpath=( $fpath )
 stty columns 80 rows 24
 LISTMAX=10000000
 ZLS_COLORS='no=<NO>:fi=<FI>:di=<DI>:ln=<LN>:pi=<PI>:so=<SO>:bd=<BD>:cd=<CD>:ex=<EX>:mi=<MI>:tc=<TC>:sp=<SP>:lc=<LC>:ec=<EC>\n:rc=<RC>'
Index: Test/ztst.zsh
===================================================================
@@ -22,6 +22,10 @@
 # still not be good enough.  Maybe we should trick it somehow.
 emulate -R zsh
 
+# Set the module load path to correspond to this build of zsh.
+# This Modules directory should have been created by "make check".
+[[ -d Modules/zsh ]] && module_path=( $PWD/Modules )
+
 # We need to be able to save and restore the options used in the test.
 # We use the $options variable of the parameter module for this.
 zmodload -i zsh/parameter
@@ -46,6 +50,9 @@
 # The source directory is not necessarily the current directory
 ZTST_srcdir=${0%/*}
 [[ $ZTST_srcdir = /* ]] || ZTST_srcdir="$ZTST_testdir/$ZTST_srcdir"
+
+# Set the function autoload paths to correspond to this build of zsh.
+fpath=( ${ZTST_srcdir:h}/(Completion|Functions)/*~*/CVS(/) )
 
 : ${TMPPREFIX:=/tmp/zsh}
 # Temporary files for redirection inside tests.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~2000-03-03 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-03 11:43 Andrej Borsenkow
2000-03-03 17:37 ` Bart Schaefer [this message]
2000-03-03 18:01   ` Blocking zpty once again Andrej Borsenkow
2000-03-03 18:23   ` PATCH: Re: Running tests without installing Zsh Zefram

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=1000303173706.ZM20761@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).