[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: testsuite failure on Solaris

From: Ralf Wildenhues
Subject: Re: testsuite failure on Solaris
Date: Sat, 22 Nov 2008 18:16:40 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

Hi Eric,

* Eric Blake wrote on Sat, Nov 22, 2008 at 05:04:39PM CET:
> Should we also patch autotest's at_fn_create_debugging_script to add 'test
> - -w "$at_group_dir" || chmod +w "$at_group_dir"', prior to attempting to
> create $at_group_dir/run, so that the first bug is not hard to re-test?

On the one hand, that sounds like a good idea to me; on the other hand,
it may be more difficult for the user to see what actually went wrong in
her third-party test suite without the clue of having an unwritable

Also, why stop at the write bit, read and execute bits don't seem in a
separate category here.  But then we arrive at quite a bit of overhead,
and quite a bit of state munging, to the point that it makes it harder
to inspect test state.

Ideally, test groups would probably have their own directory, with none
of the test suite machinery touching it at all.  But OTOH that is rather
cumbersome for the bulk of the tests one typically does.  The user can
always decide to employ directory mode hacks in a subdirectory.

So I guess I'm leaning ever so slightly towards not changing the mode,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]