On Thu, Oct 26, 2017 at 1:44 PM, Anibal Limón <limon.anibal@gmail.com> wrote:
Hi Leo,
The patch looks good at first glance, i have some comments,
- We need a way to handle the results output because with this you will have N results files, may be extend the shell script
to consolidate the results file.
As a proof of concept I use 'parallel' which fits nicely to this exercise (one job corresponds to one oe-selftest -r) and with this tool, logging can be stored in separate files, each corresponding to a job's stdout/stderr. But the important here is that the tool prints each job's output into the standard output either first-finished-first-print-to-stdout or keeping the same input order, so at the end, you get the same output as running oe-selftest as a single job.
- With this if one selftest depends on other there is no way to now it and the execution will fail, i searched into the selftest cases
(OETestDepends) and now we don't have dependent cases.
Think about this approach as running oe-selftest in different build folders with its own metadata and build folder. Under this scenario, the test execution, with the corresponding dependencies will be fulfilled and executed correctly, right? the trade off is some extra work done on each oe-selftest due to dependencies but this wont hurt much in my opinion.
Leo