W dniu 14.09.2012 16:46, Andy Doan pisze:
On 09/14/2012 09:41 AM, Zygmunt Krynicki wrote:
W dniu 14.09.2012 16:31, Andy Doan pisze:
On 09/12/2012 08:39 PM, Michael Hudson-Doyle wrote:
Andy wrote [quoting went funny somewhere]:
Here's a way we could do this in lava-test:
<http://bazaar.launchpad.net/~doanac/lava-test/software.sources-support/revision/173>
Its minimal overhead (basically none) for the test itself. However,
Michael may find it a bit odd how a bolted it on to our framework.
Thoughts?
Seems kind of OK. I don't think I have deep conceptual insight into
the
problem being solved here though :-)
Yesterday during the LAVA team meeting, we came up with a better way to
do this in code. It still doesn't cover the "99%" case, but it makes
things more transparent to the test-definition. MP to follow soon.
Cool, could you briefly describe this?
Basically add something to the installer action that lets it clone repos
rather than having be some command in the testdef we are unaware of.
+1 that's saner.
I'm worried about the lack of sensible API for stages such as this to
feed this information deeper into the core (to the initial bundle to be
precise)
PS: CCing the list again
ZK
--
Zygmunt Krynicki
s/Linaro Validation Team/Canonical Certification Team/
s/Validation/Android/
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
