From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id E02081F953; Wed, 8 Dec 2021 04:08:36 +0000 (UTC) Date: Wed, 8 Dec 2021 04:08:36 +0000 From: Eric Wong To: Julien Moutinho Cc: meta@public-inbox.org Subject: Re: Test failures with 1.7.0 Message-ID: <20211208040836.GA27368@dcvr> References: <20211208010730.f47xxgzj53nwgvja@sourcephile.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211208010730.f47xxgzj53nwgvja@sourcephile.fr> List-Id: Julien Moutinho wrote: > Hi! > > I'm trying to package the new 1.7.0 public-inbox into NixOS > at https://github.com/NixOS/nixpkgs/pull/104457 > but two reviewers are facing different test failures > that I cannot reproduce: > > One reviewer and a bot fail with: > > t/lei_to_mail.t .............. 1/? Use of uninitialized value in open at t/lei_to_mail.t line 263. > > Bailout called. Further testing stopped: No such file or directory > > FAILED--Further testing stopped: No such file or directory > > And another reviewer fails 3 times with: > > t/extsearch.t (Wstat: 2048 Tests: 145 Failed: 8) > > Failed tests: 68-69, 75-76, 86, 98, 102, 139 > > Non-zero exit status: 8 > > t/imapd.t (Wstat: 256 Tests: 186 Failed: 1) > > Failed test: 183 > > Non-zero exit status: 1 > > t/nntpd.t (Wstat: 256 Tests: 110 Failed: 1) > > Failed test: 104 > > Non-zero exit status: 1 Sorry for the problems.... I wonder if it's a missing dependency that the tests forget to account for... Can they run the tests individually using "prove" and show more output? e.g.: make && prove -bvw t/nntpd.t Also, "./lei.sh sucks" will dump the relevant deps+versions (either Inline::C or Socket::MsgHdr is required for lei to work) > Nix being Nix we can assume the exact same code is used for all, > but our systems are different (eg. CPU(s), filesystem(s), etc.) Perhaps you guys can compare installed package lists easily and help narrow it down? There's a lot of optional stuff in public-inbox since we try to support some old systems and users who don't want extra dependencies; but yes, it gets difficult to support so many possible combinations. > Could you provide some help? Hope the above was helpful, in any case I should be around-ish the next few days.