From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22420@debbugs.gnu.org
Subject: bug#22420: Zsh test failure
Date: Fri, 22 Jan 2016 15:43:06 -0500 [thread overview]
Message-ID: <20160122204306.GA27866@jasmine> (raw)
In-Reply-To: <20160122203854.GA27797@jasmine>
On Fri, Jan 22, 2016 at 03:38:54PM -0500, Leo Famulari wrote:
> On Fri, Jan 22, 2016 at 09:34:39PM +0100, Ludovic Courtès wrote:
> > Leo Famulari <leo@famulari.name> skribis:
> >
> > > I thought that perhaps it was referring to B02typeset.ztst, but I don't
> > > think there is anything related in that area of the file:
> > > 540 (
> > > 541 setopt glob
> > > 542 mkdir -p arrayglob
> > > 543 touch arrayglob/{one,two,three,four,five,six,seven}
> > > 544 fn() {
> > > 545 typeset array=(arrayglob/[tf]*)
> >
> > Out of curiosity, what file system is this on?
>
> Both filesystems are btrfs on LVM. The failing system is also using
> LUKS.
Well, actually, that only describes /home, which is perhaps not
relevant, although I did try and fail to build in a `guix environment
zsh` "by hand" in /home on the failing machine.
Failing system (separate /tmp):
/tmp /dev/mapper/bad--vg-tmp on /tmp type ext4 (rw,relatime,stripe=4,data=ordered)
Working system (/tmp on /):
/dev/mapper/good--vg-root on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
>
> >
> > Ludo’.
>
>
>
next prev parent reply other threads:[~2016-01-22 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 2:21 bug#22420: Zsh test failure Leo Famulari
2016-01-21 21:02 ` Ludovic Courtès
2016-01-21 23:05 ` Leo Famulari
2016-01-22 15:04 ` Ludovic Courtès
2016-01-22 16:30 ` Leo Famulari
2016-01-22 17:47 ` Ludovic Courtès
2016-01-22 19:33 ` Leo Famulari
2016-01-22 20:34 ` Ludovic Courtès
2016-01-22 20:38 ` Leo Famulari
2016-01-22 20:43 ` Leo Famulari [this message]
2016-01-23 10:51 ` Ludovic Courtès
2016-01-21 22:20 ` Leo Famulari
2016-01-21 23:14 ` Leo Famulari
2018-09-10 0:10 ` Leo Famulari
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=20160122204306.GA27866@jasmine \
--to=leo@famulari.name \
--cc=22420@debbugs.gnu.org \
--cc=ludo@gnu.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://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).