From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24701 invoked by alias); 2 Mar 2017 11:47:46 -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: 40695 Received: (qmail 21312 invoked from network); 2 Mar 2017 11:47:46 -0000 X-Qmail-Scanner-Diagnostics: from new1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.221):SA:0(-0.4/5.0):. Processed in 1.387955 secs); 02 Mar 2017 11:47:46 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: psprint3@fastmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spf.messagingengine.com designates 66.111.4.221 as permitted sender) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=iBiGe/BPsYLbuf8AvbmgrSbri/ g=; b=kAHiwBQ7j5SBERO3acbOd7ueYxpWK9mbeXL1rKj2MyKuGKoimbZWddzEde OcXInpldcBfmLxG1dPAeTFGzlzp0gUxrVW4bUjZvfUQyMu0AxtuidgE/csZFEHZn 2PDYYM+FygbCHqFVKYf17RRoMc99i4Cu8GgIYoxj58vxz8sXA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=iB iGe/BPsYLbuf8AvbmgrSbri/g=; b=uHDpLfeBRlXf3NOKc3Imn+ziRp3jkcxcvC v4gFFfmHO2WnsIKab1mY6tSdJkEJOxuGv9Rp7G2nQmC7aM4X2dA9cRpWEsmcXBdI /NPEHzsZiS449H51l4vubHfL40SQJs1sEaD1Jm3fz3trSZ1R9DAaIHSUPa3KccsU j63cldZME= X-ME-Sender: Message-Id: <1488455260.47056.897968424.73CCAA35@webmail.messagingengine.com> From: Sebastian Gniazdowski To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-715c2c0c References: <22600020-4905-4E9B-86DE-663907DBB39C@kba.biglobe.ne.jp> In-Reply-To: <22600020-4905-4E9B-86DE-663907DBB39C@kba.biglobe.ne.jp> Subject: Re: V11db_gdbm.ztst fails on Cygwin Date: Thu, 02 Mar 2017 03:47:40 -0800 On Thu, Mar 2, 2017, at 02:52 AM, Jun T. wrote: > @@ -1,4 +1,4 @@ > -c > -d > a > b > +c > +d > > ${(k)dabse} gives 'a c', instead of 'c a' as expeced by the test. > The order the records are visited by gdbm_{firstkey,nextkey}() > depends on the hash values used by gdbm, and (due to some reason > unknown to me) it seems the hash values used on Cygwin are different > from those used on Linux. (...) > Is it really necessary to test that gdbm_{firstkey,nextkey}() > gives the same order on different OSs? Was counting on determinism here. A fragile thing, but determinism should guarantee this. Wonder why Cygwin's gdbm flips order. Any idea how to write test result so that both hash key orders match? -- Sebastian Gniazdowski psprint3@fastmail.com