Hi Sakib, On Mon, 2021-03-08 at 15:46 -0500, Sakib Sajal wrote: > Randy and I could directly use autobuilders and make the necessary > changes to run the tests/experiments, if you prefer to do it yourself, > read on for more details.
I'm happy to have the help. I'm thinking that rather than instrument one build or a specific test case, we should add something to yocto-autobuilder-helper on a test branch, that way we can run an "a-full" or "a-quick" target on the autobuilder under the test and see if we can get any interesting data. The autobuilders have a shared output directory we could use to collate the information, it is exported to the environment as OEQA_DEBUGGING_SAVED_OUTPUT in config.json in -helper. I think we therefore need: a) poky-contrib branch with this change in b) yocto-autobuilder-helper branch with the config enabled in config.json c) a further patch to collect up any interesting data and save it to OEQA_DEBUGGING_SAVED_OUTPUT as a post build event handler for further analysis. We may be able to patch the existing results collection script to do this in helper? Obviously the naming of the files on OEQA_DEBUGGING_SAVED_OUTPUT needs to be multi build safe. Does that sound like a reasonable approach? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#149127): https://lists.openembedded.org/g/openembedded-core/message/149127 Mute This Topic: https://lists.openembedded.org/mt/81158947/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
