From: Nils Gillmann <ng0@n0.is>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Redefining the maximum path length [Fwd: Re: [GNUnet-developers] using $TMPDIR instead of /tmp]
Date: Sun, 6 May 2018 20:17:20 +0000 [thread overview]
Message-ID: <20180506201720.ag4u6irpwh4ibnsy@abyayala> (raw)
In-Reply-To: <20180506194950.GC8038@jasmine.lan>
Leo Famulari transcribed 3.0K bytes:
> On Sun, May 06, 2018 at 07:27:46PM +0000, Nils Gillmann wrote:
> > I have inserted a build log of a failing test from
> > GNUnet commit f13af7e7281064380def70d0b4392b4351211655
>
> [...]
>
> > TEST: Viewing all stats...FAIL: unexpected output:
> > osystem other: 43
> > subsystem test: 42
> > !test-statistics-api test-3: 3
> >
> > FAIL test_gnunet_statistics.py (exit status: 1)
>
> [...]
>
> > Human addition:
> > make[4]: *** [Makefile:1074: test-suite.log] Error 1
> > make[4]: Leaving directory '/tmp/guix-build-gnunet-git1.drv-0/source/src/statistics'
> > make[3]: *** [Makefile:1182: check-TESTS] Error 2
> > make[3]: Leaving directory '/tmp/guix-build-gnunet-git1.drv-0/source/src/statistics'
> > make[2]: *** [Makefile:1281: check-am] Error 2
> > make[2]: Leaving directory '/tmp/guix-build-gnunet-git1.drv-0/source/src/statistics'
> > make[1]: *** [Makefile:550: check-recursive] Error 1
> > make[1]: Leaving directory '/tmp/guix-build-gnunet-git1.drv-0/source/src'
> > make: *** [Makefile:591: check-recursive] Error 1
> > phase `set-path-for-check' failed after 29.2 seconds
> > note: keeping build directory `/tmp/guix-build-gnunet-git1.drv-0'
> > builder for `/gnu/store/daqbvvd3zq2w1aw6w4yz5qm7s5k247ap-gnunet-git1.drv' failed with exit code 1
> > @ build-failed /gnu/store/daqbvvd3zq2w1aw6w4yz5qm7s5k247ap-gnunet-git1.drv - 1 builder for `/gnu/store/daqbvvd3zq2w1aw6w4yz5qm7s5k247ap-gnunet-git1.drv' failed with exit code 1
> > guix build: error: build failed: build of `/gnu/store/daqbvvd3zq2w1aw6w4yz5qm7s5k247ap-gnunet-git1.drv' failed
>
> [...]
>
> > With this we get filenames like:
> > /tmp/guix-build-gnunet-git1.drv-0/gnunet/test-gnunet-statistics/.local/share/gnunet/statistics.dat
> > which is an average length. When you just do it in /tmp, you won't experience any difficulties.
>
> That path is only 98 characters long. What limit do you think it is
> exceeding?
Right, I provided too little context of the log.
Okay, the error is elsewhere in this case, not the path length..
But on topic, I've run into the UNIX_PATH_LENGTH error a couple of times
before when the package name was longer, but not unusual long (let's say
gnunet-variant-flavor-bla.. A little room to wiggle for applications that
do not consider folder naming with the checksums, would be good.
Obviously so far these are corner cases, but even if we decide that we
would not need it today, a discussion if this is something that can be
done, etc etc would be good.
From memory, I think I've only ever encountered this in C based applications
test suites. Everything else just worked.
next prev parent reply other threads:[~2018-05-06 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 18:59 Redefining the maximum path length [Fwd: Re: [GNUnet-developers] using $TMPDIR instead of /tmp] Nils Gillmann
2018-05-06 19:11 ` Leo Famulari
2018-05-06 19:27 ` Nils Gillmann
2018-05-06 19:49 ` Leo Famulari
2018-05-06 20:17 ` Nils Gillmann [this message]
2018-05-07 5:03 ` Pjotr Prins
2018-05-07 16:37 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180506201720.ag4u6irpwh4ibnsy@abyayala \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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://git.savannah.gnu.org/cgit/guix.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).