Re: [RFA] fix remote testing I/O conflicts

2016-03-07 Thread Ben Elliston
On Mon, Mar 07, 2016 at 05:16:12PM +0700, Rob Savoye wrote: > I'll look into this, not sure if anyone else but Linaro is doing > multiple builds in parallel. I think I lean towards the "/tmp/pid/" > solution. I don't believe this would break anything else, but would > of course want to make the

Re: [RFA] fix remote testing I/O conflicts

2016-03-07 Thread Rob Savoye
On 03/03/2016 01:45 AM, Yvan Roux wrote: > To fix this issue, changing the layout to have the testcases > downloaded and executed inside "/tmp/pid/" directory would do the job, > but as this change might have an impact on other project or on other > config which use remote_download, my proposal is

Re: [RFA] fix remote testing I/O conflicts

2016-03-07 Thread Yvan Roux
Hey Rob, On 7 March 2016 at 11:16, Rob Savoye wrote: > On 03/03/2016 01:45 AM, Yvan Roux wrote: > >> To fix this issue, changing the layout to have the testcases >> downloaded and executed inside "/tmp/pid/" directory would do the job, >> but as this change might have an impact on other project o

Re: [Patch] Fix output pattern checking issue

2016-03-07 Thread Yvan Roux
Hi Ben On 4 March 2016 at 23:35, Ben Elliston wrote: > On Fri, Mar 04, 2016 at 10:20:57PM +0100, Yvan Roux wrote: > >> there is an issue when remote testing testcases which check an >> output pattern with an explicit '\n' at the end. rsh_exec >> explicitly removes it to behave as 'exec', I don't