[Automated-testing] [yocto-builds] Executing gcc and gdb test suites
Mark Hatle
mark.hatle at windriver.com
Tue Apr 17 06:35:44 PDT 2018
On 4/17/18 7:59 AM, Burton, Ross wrote:
> On 13 April 2018 at 16:23, Mark Hatle <mark.hatle at windriver.com> wrote:
>> But at Wind River we run dejagnu (included with the toolchain) as part of our
>> our toolchain validation. This will cover most regression situations and is a
>> really good sanity test that things are working in a reasonable way.
>>
>> This is something that could be extended into the Yocto Project (open embedded)
>> environment. It would be a natural fit to the 'ptest' infrastructure. The only
>> real issue is that dejagnu is known to now pass with a 100% rate, so you really
>> need multiple runs to watch for regressions.
>
> Mark, could you file an enhancement bug in the Yocto bugzilla for
> this? And ideally a mini-howto of how to run dejagnu...
I don't have the steps, a different team does this work.
My goal is to try to get them to either implement this [as a ptest], or possibly
the instructions so I can do it instead.
Their existing work is always verified based on generated SDKs, and an external
invocation of dejagnu.
--Mark
> Cheers,
> Ross
>
More information about the automated-testing
mailing list