The current tests for build appliance located in https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=6552 need to be updated to remove HOB and need to be automated so that the Build Appliance can act as a dogfooding test environment.
I have updated the cases in https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=6552
Hi Brain, I have no idea about how to automated these cases. Do you mean we should automated all steps include start a vmplayer to launch BA, login and perform the test cases or just automated the test cases in a launched BA ?
Ideally, this would be a script that launched the player/VirtualBox, with the BA as a target. Juro suggests 8 gb mem and 8 cpus. Caveat: Vmplayer fails for Juro on Linux. There is a networking readme in the BA docs, to explain how to set up the BA in nat mode with port forwarding which would be deterministic. This will also help if we decide to test toaster in the 2.4 timeframe on BA. Then I'd use a script to ssh in and run the tests like our other tests (testimage for instance) run. Alternatively, we could just build core-image-minimal and run the testimage itself on the BA. That would be fairly easy and more complete than the current test. Fair Warning: Current BA is broken due to a bash etc/alternative move issue. This approach could be easily fleshed out against morty and moved to master once the BA is back working. -- Juro said to ask if you hit roadblocks.
I believe the question is answered
Created attachment 3805 [details] ba-auto-test.sh The attachment is a script for ba testing automation. The script does the following things: 1. Connect the BA VM and set the build environment. 2. Choose a qemu arch randomly and build a minimal image. 2. Run self test for this image.
The script works well on Yocto 2.3 BA
The script is a great start but it's not enough to mark this issue resolved. We need to ensure that test is used as part of our automated testing so that we can detect when the build appliance is broken.
(In reply to comment #8) > The script is a great start but it's not enough to mark this issue resolved. > We need to ensure that test is used as part of our automated testing so that > we can detect when the build appliance is broken. Thanks Joshua. I will do more work with it.
QA Penang needs to analyse this from the beginning, with Yi's help.
QA team had created the manual build appliance test cases and shared the build appliance testing information to the community. Also QA team had made the decision to discontinue build appliance manual testing given limited resource available. QA team currently looking for community to provide build appliance automation if it was still needed. http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/manual/build-appliance.json
Still needs to be done.
Bulk move from 4.99 or 0.00 to 5.99
Marking as a duplicate (in the future) of 16016 as BA is rarely used now. *** This bug has been marked as a duplicate of bug 16016 ***