And when a bug creeps in and destroy's someone's system? We already
destroyed one user's entire system with a bug in panda. It wasn't a
pretty picture.
It's fine to check failure modes on an existing directory we create
during testing, but I'm a definite -1 on attempting to much around
with '/'
Cheers,
ZZ
Quoting Brandon Allbery <allber...@gmail.com>:
On Mon, Jul 4, 2016 at 6:44 PM, Zoffix Znet via RT <
perl6-bugs-follo...@perl.org> wrote:
> Ticket should be closable once a test has been added to Roast.
Is it really appropriate to attempt to create such directories? I'm
hesitant to have roast touch things outside of its directory.
It's a directory that must always exist and therefore always fail in a
consistent way.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
