From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32083-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 19519 invoked by alias); 2 Dec 2013 17:48:53 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 32083
Received: (qmail 10635 invoked from network); 2 Dec 2013 17:48:46 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <131202094901.ZM22025@torch.brasslantern.com>
Date: Mon, 02 Dec 2013 09:49:01 -0800
In-reply-to: <20131202172028.GW13790@sym.noone.org>
Comments: In reply to Axel Beckert <abe@deuxchevaux.org>
 "One test suite failure left on static build (after $HOME has been fixed)"
 (Dec  2,  6:20pm)
References: <20131201194653.7a98a4a4@pws-pc.ntlworld.com>
	<20131202155119.GR13790@sym.noone.org>
	<20131202160133.7d77d7be@pwslap01u.europe.root.pri>
	<20131202161616.GS13790@sym.noone.org>
	<131202084329.ZM3583@torch.brasslantern.com>
	<20131202164811.GU13790@sym.noone.org>	<20131202165745.GV13790@sym.noone.org>
	<20131202172028.GW13790@sym.noone.org>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: One test suite failure left on static build (after $HOME has been
 fixed)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Dec 2,  6:20pm, Axel Beckert wrote:
}
} Leaves this test suite error:
} 
} ../../Test/C02cond.ztst: starting.
} Test ../../Test/C02cond.ztst failed: bad status 1, expected 0 from:
}   if (( EUID == 0 )); then
}     print -u$ZTST_fd 'Warning: Not testing [[ ! -r file ]] (root reads anything)'
}     [[ -r zerolength && -r unmodish ]]
}   elif [[ $OSTYPE = cygwin ]]; then
}     print -u$ZTST_fd 'Warning: Not testing [[ ! -r file ]]
}    (all files created by user may be readable)'
}    [[ -r zerolength ]]
}   else
}     [[ -r zerolength && ! -r unmodish ]]
}   fi
} Was testing: -r cond

This could be a umask issue, there's an implicit assumption that

    umask 077
    touch zerolength
    chgrp $EGID zerolength

will create a readable file, and that

    touch unmodish
    chmod 000 unmodish

will create an UNreadable file.  Unfortunately it's not possible to
tell from the test which one of (-r zerolength) or (! -r unmodish)
failed.  I have no idea why running this in the package build would
affect this, though.