Hi, On Wed, Mar 09, 2016 at 11:10:41PM +0000, Fabien Siron wrote: > Hello list, > > Before trying to apply for GSOC, I think it's a really good idea to make > a first contribution. Thus, it seems that an easy and useful contribution > would be a test.
Definitely. As virtually every GSoC project expects writing some tests, the experience of extending test suite would be useful anyway. > I noticed that a chmod test has been recently added to > the project and I think that complete the *chmod family* test could be > good. But I have two questions: > > * Does this choice of test is a good one? Neither fchmod nor fchmodat is covered by the test suite yet: $ git grep fchmod tests/ | wc -l 0 I think you've made a good choice, fchmodat is more interesting than plain chmod and still reasonably easy to start with. > * If yes, do fchmod and fchmodat have to be tested in the same test as > chmod or in a separated one? Some modern architectures don't implement chmod syscall, and relatively old kernels don't implement fchmodat. Even for this simple reason all these syscalls have to be tested separately. -- ldv
pgpf4ccD9YVVI.pgp
Description: PGP signature
------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________ Strace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/strace-devel
