From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5980 invoked from network); 1 Jun 2000 10:03:54 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Jun 2000 10:03:54 -0000 Received: (qmail 5602 invoked by alias); 1 Jun 2000 10:03:40 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11710 Received: (qmail 5595 invoked from network); 1 Jun 2000 10:03:40 -0000 Date: Thu, 01 Jun 2000 11:03:10 +0100 From: Peter Stephenson Subject: Re: Output of 'make check' In-reply-to: "Your message of Thu, 01 Jun 2000 13:28:08 +0400." <000501bfcbab$b2aad710$21c9ca95@mow.siemens.ru> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FVG001HSZXA60@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT > I do not particular like it. It outputs thousands of "No differences > encountered", that will scroll away any useful output. So, if any test > in between fails, there is no chance to see it unfortunately (there > seems to be no log by default). I just noticed, that one more test > failed - and it was only by accident. That's coming from your version of diff, not the test harness. If you can find a portable way of suppressing it without removing the useful output, I will add it --- it may simply be a case of 2>/dev/null. I'm getting the _arguments test failure you report, too, but _arguments is not something I'd like to see changed at this stage, since a lot of the completion system depends on quite small details of how it works. We can leave the test out for the time being. We could create a separate set of tests known to fail, not run by default but designed to embarrass the developers. I'm not sure how much I like the sound of that. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070