9460 2016-04-13 22:22:36 +0000 Provide a way to automate testing of meta-mingw 2017-12-06 16:52:52 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 2.2 x86 Multiple RESOLVED FIXED Medium+ enhancement 2.3 M3 10914 10971 1 juro.bystricky joshuagloe benjamin.esquivel brian.avery elizabeth.flanagan infras.ab.watcher Infras.watcher jose.perez.carranza joshuagloe sgw sonia.delgado --- --- Don't know oldest_to_newest 61181 0 juro.bystricky 2016-04-13 22:22:36 +0000 Provide a way to automate testing of meta-mingw and meta-darwin layers. These two layers are officially supported by the Yocto project, but there are no automated tests (that I know of) that target these layers. Probably the most common usage of those meta layers are cross-compiled toolchains, so that would make them the prime candidates for automated testing. 63675 1 joshuagloe 2016-07-06 16:03:16 +0000 An initial step towards automating testing of these layers is to have them integrated into a buildset and built on the autobuilder, thus at least testing the builds are successful. This is why the issue is filed against the autobuilder, which confused this reader on first reading this report. A future step may be to develop automated tests for them, but that should likely be a separate ticket. Note: the meta-darwin build is problematic. The layer requires files be extracted from a Mac OS SDK and we don't have permissions to distribute these files, therefore a meta-darwin build on the public autobuilder will be problematic. 65316 2 brian.avery 2016-08-18 17:00:34 +0000 for meta-darwin I'd consider using TravisCI for the tests. If you run it as an objective c test, you get an OSX environment. https://docs.travis-ci.com/user/languages/objective-c 65490 3 brian.avery 2016-08-24 16:06:20 +0000 https://www.appveyor.com/docs/running-tests/ can test windows instantiations. 66085 4 benjamin.esquivel 2016-09-13 14:20:05 +0000 I believe that meta-darwin and meta-mingw can be a target for creating tests for the 2.3 release. CC'ing QA so they can file the bugs as necessary. based on the description of meta-darwin and meta-mingw: OpenEmbedded meta layer for [darwin|mingw] based SDKs. The first approach could be to add oe-selftest cases to the layers then it should be decided whether to execute them along with the nightly-oe-selftest or create a separate one. 69709 5 joshuagloe 2017-01-11 14:22:43 +0000 I'm moving out the meta-darwin piece into a separate bug as that's more complicated and requires access to a macOS install. See bug 10912. Adding a meta-mingw builder is much simpler and something we can easily provide for 2.3 69714 6 joshuagloe 2017-01-11 14:53:12 +0000 I have an implementation of a minimal builder config which calls: $ bitbake core-image-sato core-image-minimal -c populate_sdk $ bitbake core-image-sato core-image-minimal -c testsdk I can't test it because of bug 10914 69957 7 joshuagloe 2017-01-20 13:21:26 +0000 http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=ac756a4d94627692da2dd0fa9c523f8402a540f1 70172 8 joshuagloe 2017-01-26 11:35:34 +0000 Dependent bug was closed after M2 rc1 had been built, moving this to M3 70691 9 joshuagloe 2017-02-14 16:27:31 +0000 meta-mingw build added to nightly-qa-extras and deployed to both AB clusters: http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=ac756a4d94627692da2dd0fa9c523f8402a540f1 http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=e791185ce086dd9b48f0f006c7eab2da561aec7a http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=7ff32480c118cf0f39db90bd6d47bd5819eed633