<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">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.<div><br></div><div>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.</div><div><br></div><div>Meanwhile you can install the stack by finding the pex_policy package (where it was built), declaring it and then resuming the automated build.</div><div><br></div><div>The command to declare it to eups is:</div><div>eups declare -r <path to the package> pex_policy 10.0-1-g0f53050+14</div><div><br></div><div>You may also want to specify a tag by appending: -t <tag></div><div>you can see what tags were used for one of the LSST packages that was successfully installed. For a list of all packages:</div><div>eups list</div><div><div><br></div><div>-- Russell</div><div><br><div><div>On Apr 30, 2015, at 12:45 PM, Alex Kim <<a href="mailto:agkim@lbl.gov">agkim@lbl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<span id="mailbox-conversation">Indeed I see that out of the box users don’t have write permissions to /etc/motd. </span><div class="mailbox_signature"><br></div>
<br><br><div class="gmail_quote"><p>On Thu, Apr 30, 2015 at 11:59 AM, Alex Kim <span dir="ltr"><<a href="mailto:agkim@lbl.gov" target="_blank">agkim@lbl.gov</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<span id="mailbox-conversation"><div>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?</div>
<div><br></div>
<div>Alex</div>
<div></div></span><div class="mailbox_signature"><br></div>
<br><br><div class="gmail_quote"><p>On Thu, Apr 30, 2015 at 11:23 AM, Russell Owen <span dir="ltr"><<a href="mailto:rowen@uw.edu">rowen@uw.edu</a>></span> wrote:<br></p>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p>It would help to see the log of the failed test. Look in the directory where pex_policy was built, in tests/.tests/*.failed
<br><br>-- Russell
<br><br>On Apr 30, 2015, at 10:57 AM, Alex Kim <<a href="mailto:agkim@lbl.gov">agkim@lbl.gov</a>> wrote:
<br><br>> <build.log>
<br><br></p></blockquote>
</div>
<br></div>
<mailbox-attach src="mailbox://attachment_download/897EB848-E309-4219-99B0-69E1B480D68C/29190BB1-67FD-4D67-85FD-5B2DA5AC0889/2" filename="testBadPAFWrite.failed" mime="application/octet-stream" size="191"><testBadPAFWrite.failed></mailbox-attach></blockquote></div><br></blockquote></div><br></div></div></body></html>