[LSST|dm-users 599] Re: Failed pex_policy test for OS X Yosemite install

[Russell Owen]

It is an interesting test. It wants /etc to be unwritable and it wants the attempt to write to raise an exception. The exception is not raised in this case, so the test fails.

I am a bit puzzled why we would write a test that relies on /etc to be unwritable. I would have thought it safer to create a directory somewhere (e.g. in /tmp or pex_policyt/tests) that is unwritable and use that. However, this is a package we are trying to stop using, so I wonder if the best solution might be to simply get rid of this test, rather than rewriting it. Sounds like a discussion for HipChat.

Meanwhile you can install the stack by finding the pex_policy package (where it was built), declaring it and then resuming the automated build.

The command to declare it to eups is:
eups declare -r <path to the package> pex_policy 10.0-1-g0f53050+14

You may also want to specify a tag by appending: -t <tag>
you can see what tags were used for one of the LSST packages that was successfully installed. For a list of all packages:
eups list

-- Russell

On Apr 30, 2015, at 12:45 PM, Alex Kim <agkim at lbl.gov> wrote:

> Indeed I see that out of the box users don’t have write permissions to /etc/motd. 
> 
> 
> 
> On Thu, Apr 30, 2015 at 11:59 AM, Alex Kim <agkim at lbl.gov> wrote:
> 
> Here is the log file of the failed test.  It looks like a permissions problem.  I don’t have to install as root, do I?
> 
> Alex
> 
> 
> 
> On Thu, Apr 30, 2015 at 11:23 AM, Russell Owen <rowen at uw.edu> wrote:
> 
> It would help to see the log of the failed test. Look in the directory where pex_policy was built, in tests/.tests/*.failed 
> 
> -- Russell 
> 
> On Apr 30, 2015, at 10:57 AM, Alex Kim <agkim at lbl.gov> wrote: 
> 
> > <build.log> 
> 
> 
> 
> <testBadPAFWrite.failed>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lsst.org/pipermail/dm-users/attachments/20150430/8b83df3d/attachment.html>