From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18180 invoked by alias); 2 Mar 2017 11:28:21 -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: 40694 Received: (qmail 13953 invoked from network); 2 Mar 2017 11:28:21 -0000 X-Qmail-Scanner-Diagnostics: from rcpt-mqugw.biglobe.ne.jp 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(133.208.100.4):SA:0(-0.7/5.0):. Processed in 0.709561 secs); 02 Mar 2017 11:28:21 -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.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: takimoto-j@kba.biglobe.ne.jp X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spf01.biglobe.ne.jp designates 133.208.100.4 as permitted sender) X-Biglobe-Sender: From: "Jun T." Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: V11db_gdbm.ztst fails on Cygwin Message-Id: <22600020-4905-4E9B-86DE-663907DBB39C@kba.biglobe.ne.jp> Date: Thu, 2 Mar 2017 19:52:39 +0900 To: "zsh-workers@zsh.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-Biglobe-Spnum: 57487 V11db_gdbm.ztst fails on Cygwin as: ./V11db_gdbm.ztst: starting. --- /tmp/zsh.ztst.2148/ztst.out 2017-03-02 19:26:45.040189100 +0900 +++ /tmp/zsh.ztst.2148/ztst.tout 2017-03-02 19:26:45.055788600 = +0900 @@ -1,4 +1,4 @@ -c -d a b +c +d Test ./V11db_gdbm.ztst failed: output differs from expected as shown = above for: ztie -d db/gdbm -f $dbfile dbase dbase=3D( a b c d ) zuntie dbase ztie -d db/gdbm -f $dbfile dbase print -rl -- "${(kv)dbase[@]}" zuntie dbase Was testing: replace hash / database, scan ./V11db_gdbm.ztst: test failed. ${(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. The gdbm I'm using on Cygwin is from the Cygwin's package repository (binary distribution). Is it really necessary to test that gdbm_{firstkey,nextkey}() gives the same order on different OSs? PS On macOS V11db_gdbm.ztst succeeds (with gdbm built by myself from the gdbm source).=