user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: meta@public-inbox.org
Subject: Re: Test failures in build sandbox
Date: Thu, 26 Sep 2019 08:44:31 +0000	[thread overview]
Message-ID: <20190926084431.ukv53sfskk7qvere@dcvr> (raw)
In-Reply-To: <87r245tkbz.fsf@alyssa.is>

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

  reply	other threads:[~2019-09-26  8:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 13:48 [PATCH] t/spawn: fix with unusual env locations Alyssa Ross
2019-09-15 18:55 ` Eric Wong
2019-09-24  1:11   ` Alyssa Ross
2019-09-24  4:01     ` Eric Wong
2019-09-24 22:12       ` Test failures in build sandbox Alyssa Ross
2019-09-26  8:44         ` Eric Wong [this message]
2019-10-02 23:23           ` Alyssa Ross
2019-10-03  0:46             ` Alyssa Ross
2019-10-03  1:28               ` Eric Wong
2019-10-03  1:43                 ` Alyssa Ross
2019-10-03  7:57                   ` [PATCH] t/search: bail out on `git init --shared' failures Eric Wong
2019-10-03 10:15                     ` Alyssa Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190926084431.ukv53sfskk7qvere@dcvr \
    --to=e@80x24.org \
    --cc=hi@alyssa.is \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).