From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
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 7BD9D1F463;
	Thu, 26 Sep 2019 08:44:31 +0000 (UTC)
Date: Thu, 26 Sep 2019 08:44:31 +0000
From: Eric Wong <e@80x24.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: meta@public-inbox.org
Subject: Re: Test failures in build sandbox
Message-ID: <20190926084431.ukv53sfskk7qvere@dcvr>
References: <20190915134819.1406-1-hi@alyssa.is>
 <20190915185519.GA4891@dcvr>
 <87zhiu4hxl.fsf@alyssa.is>
 <20190924040123.6jbtvpadnk6negox@whir>
 <87r245tkbz.fsf@alyssa.is>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87r245tkbz.fsf@alyssa.is>
List-Id: <meta.public-inbox.org>

Alyssa Ross <hi@alyssa.is> wrote:
> Eric Wong <e@80x24.org> writes:
> 
> >> (It may be of note however that I did not have Xapian enabled.  Trying
> >> to build with that caused a host of other failures that were beyond my
> >> ability to troubleshoot, so I decided to just give up on running the
> >> tests for now, since they seem very dependent on the environment and the
> >> environment inside our build sandboxes is so different from what
> >> public-inbox will have on a running system anyway.)
> >
> > I don't know much about Nix, but I hope/expect public-inbox
> > tests to work on every reasonably modern Unix-like OS which
> > Perl5, git, and SQLite run on.
> >
> > If you post logs of the failures you encountered, it would
> > improve the chances that somebody here (maybe not me) can
> > help fix them.  Thanks.
> 
> As requested, following a test log, edited down to just failures /
> successes with error output:

Thanks.

> PERL_DL_NONLAZY=1 "/nix/store/5r85g4zzk0djffzs47zaimvkxfmbpp3q-perl-5.30.0/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/convert-compact.t ........ 1/? error: unable to create temporary file: Operation not permitted
> fatal: failed to write object

What kind of filesystem and mount options was the code and
(if set, TMPDIR) on?

Since Nix seems to use odd paths, what's the default temporary
directory? ("/tmp" on my systems)

AFAIK, it should be possible to run tests with the
source/worktree on a read-only FS (only TMPDIR needs to be
writable); but it's not something that's fun/quick to test.

> t/search.t ................. fatal: Could not make /build/pi-search-i646IK/a.git/branches/ writable by group
> t/search.t ................. 1/?
> #   Failed test 'git init (main)'
> #   at t/search.t line 20.
> #          got: '0'
> #     expected: '32768'
> 
> #   Failed test 'undefined permission is group'
> #   at t/search.t line 40.
> #          got: '0'
> #     expected: '432'
> t/search.t ................. 92/?
> #   Failed test 'sharedRepository respected for msgmap.sqlite3'
> #   at t/search.t line 455.
> #          got: '420'
> #     expected: '432'
> 
> #   Failed test 'sharedRepository respected for public-inbox'
> #   at t/search.t line 455.
> #          got: '493'
> #     expected: '1528

<snip>

Sidenote, it would be easier to read if Test::More output those
as octal numbers.  I use iprint ("i") from Debian oldstable
installs, but it's no longer in Debian buster :<

printf '%0o\n' 493
printf '%0o\n' 1528
...
works, too, but it's more typing