zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: make check failures in latest CVS
Date: Wed, 9 Feb 2000 09:45:37 +0100 (MET)	[thread overview]
Message-ID: <200002090845.JAA06656@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Vin Shelton's message of 08 Feb 2000 20:14:26 -0500


Vin Shelton wrote:

> For the last 2 days the CVS snapshots have failed 'make check' with the
> following error:
> 
> *** /tmp/zsh.ztst.out.1405      Tue Feb  8 20:03:54 2000
> --- /tmp/zsh.ztst.tout.1405     Tue Feb  8 20:03:54 2000
> ***************
> *** 1,2 ****
> - Line 1
> - Line 1
> --- 0 ----
> Test /usr/local/src/zsh-2000-02-08/Test/05command.ztst failed: output differs from expected as shown above for:
>   unfunction fn
>   print 'TRAPDEBUG() {
>       print Line $LINENO
>     }
>     :
>     unfunction TRAPDEBUG
>   }' > fn
>   autoload fn
>   fn
>   rm fn
> Error output:
> fn:6: parse error near `}'
> Was testing: TRAPDEBUG
> /usr/local/src/zsh-2000-02-08/Test/05command.ztst: test failed.

That's a result of my patch that made parse errors in autoloaded
functions be shown. And, as you can see above, it was right, the
typo(s) were in 05command.ztst.

Bye
 Sven

--- Test/05command.ztst.old	Wed Feb  9 09:43:40 2000
+++ Test/05command.ztst	Wed Feb  9 09:43:44 2000
@@ -116,7 +116,7 @@
     }
     :
     unfunction TRAPDEBUG
-  }' > fn
+  ' > fn
   autoload fn
   fn
   rm fn
@@ -128,7 +128,7 @@
   print 'trap '\''print Line $LINENO'\'' DEBUG
     :
     trap - DEBUG
-  }' > fn
+  ' > fn
   autoload fn
   fn
   rm fn

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-02-09  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-09  8:45 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-09  1:14 Vin Shelton

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=200002090845.JAA06656@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).