From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21620 invoked by alias); 31 Jan 2016 20:25:20 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 37854 Received: (qmail 5344 invoked from network); 31 Jan 2016 20:25:16 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_PCNT autolearn=no autolearn_force=no version=3.4.0 Date: Sun, 31 Jan 2016 21:19:34 +0100 From: Axel Beckert To: zsh-workers@zsh.org Cc: Debian Zsh Maintainers Subject: Strange test suite behaviour since zsh 5.2-dev-1: C02cond.ztst no more reports its finishing Message-ID: <20160131201933.GL4726@sym.noone.org> Mail-Followup-To: zsh-workers@zsh.org, Debian Zsh Maintainers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: Linux 3.2.0-4-amd64 X-Machine: sym2 x86_64 X-Editor: GNU Emacs 23.4.1 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAAAAAC3mUtaAAAABGdBTUEAALGPC/xhBQAAADh0RVh0U29mdHdhcmUAWFYgVmVyc2lvbiAzLjEwYSAgUmV2OiAxMi8yOS85NCAoUE5HIHBhdGNoIDEuMindFS5JAAACGElEQVQ4jXXQMU8UYRDG8f8shNjdDH4AbpfGDjAWlKiJiZ0ajL1aGCvsNCbGaCGG1koLaztaTYz6ATy+gOyehYmF3MxVxgg3FnDsHcTpJr/M+8w7Rf6nCsaVTTDqxbg9hoOXmw83H71+Eyfg4E1d7/Z2fG9rGkZbTQiu+K+3U/C+76lmkvAhJuDndnoAiftou4V84okAGclop4U/jYACZDTxrYWP0gkxVfAm/W//GLZpxIzwIN0Hn8dw0B+IWkZmQmRsj2HfhwokEklHfNCCiQCRgAR7YyhQVRVTCKCzP4Y5zBBE0t0zY3Q8oQaBqqAMlVEcgVQd9706zGirAFium8HXumlMIeMwqQCInju+2+uB6MRENupdpMt8pRlHZyuAW0F+Mb6XSIVqtxjD+iVmVqqystLEzFTGT92YqRaXpNT5eTVjeJhbALPnrTxLUZUKZsgxcNm64hAOYisT/xhF+oKTGU5RegtC3Rt6eEDi/QnIevdTx9Md2EMmYBRmCQR1026FCGQQJJExsRUqgkMGaWSbwYLnoO4T6VgpbQbdELPMBAHWWrhYrcxXnYgAsatPWygkFCBD4K62MAsOTqA6szYRPpsu6e6Y8mPiVrBMNuGIMrgwBUu4p2DgG1Ownu6hpuTv7hScefHAzAC/yRRw5U5pALMbJ4AUALvHSZhxgHPXTsHcdWD1GadAHr9avP+c0wCr7263Df8ASLwXWHWs+KIAAAAHdElNRQfYBQEBODPr Organization: DeuxChevaux.org -- The =?iso-8859-1?Q?Citr?= =?iso-8859-1?B?b+tu?= 2CV Database User-Agent: Mutt/1.5.21 (2010-09-15) Hi, I've seen this locally only once (on x86_64) once (IIRC when enabling -fPIE for one test build), but on x86 (32 bit) the following issue has been observed on our (Debian Zsh Packaging Team) Jenkins since I pushd 5.2-dev-1 (http://jenkins.grml.org/view/Debian/job/zsh-binaries/architecture=i386/): >>From the log of the test suite (examples taken from http://jenkins.grml.org/view/Debian/job/zsh-binaries/architecture=i386/251/console): […] 20:56:44 Running test: type of variable when created in arithmetic context 20:56:44 Test successful. 20:56:44 ../../Test/C01arith.ztst: all tests successful. 20:56:44 ../../Test/C02cond.ztst: starting. 20:56:44 Running test: -a cond 20:56:44 Test successful. […] 20:56:46 Running test: test with two arguments and a token 20:56:46 Test successful. 20:56:46 Running test: yet more old-fashioned test fix ups: prefer comparison to parentheses 20:56:46 ../../Test/C03traps.ztst: starting. 20:56:46 Running test: Nested `trap ... EXIT' 20:56:46 Test successful. […] What I miss is the "Test successful." for "yet more old-fashioned test fix ups: prefer comparison to parentheses" as well as the "../../Test/C02cond.ztst: all tests successful.". Even if "yet more old-fashioned test fix ups: prefer comparison to parentheses" did fail, I'd expect that it at least reports that fact. But it looks as if the whole test script just silently exits. In comparison, the x86_64 test suite runs look fine (taken from http://jenkins.grml.org/view/Debian/job/zsh-binaries/architecture=amd64/251/consoleFull): […] 20:47:55 Running test: type of variable when created in arithmetic context 20:47:55 Test successful. 20:47:55 ../../Test/C01arith.ztst: all tests successful. 20:47:55 ../../Test/C02cond.ztst: starting. 20:47:56 Running test: -a cond 20:47:56 Test successful. […] 20:47:58 Running test: yet more old-fashioned test fix ups: prefer comparison to parentheses 20:47:58 Test successful. 20:47:58 ../../Test/C02cond.ztst: all tests successful. 20:47:58 ../../Test/C03traps.ztst: starting. 20:47:58 Running test: Nested `trap ... EXIT' 20:47:58 Test successful. […] Any ideas what could cause this silent exiting of a .ztst script and why it only appears under certain (yet not 100% clear) conditions? Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)