| Age | Commit message (Collapse) | Author |
|---|
|
Check that yocto-autobuilder-helper has been cloned to the correct location.
Check that vnc is running using the same script the autobuilder does.
Set the DISPLAY enviroment variable to :1 the same way we do when building
normally.
Make the VM's serial console available so we can log in and power off allowing
the tests to continue.
Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Temporarily modify path to run as non-privileged user on more distros.
Change the recommended value to match what we use on the autobuilder.
Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Note further tests needed after encountering issues.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Add a couple of missing items to the TODO list that this script needs to handle.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Add a script which can be run on new autobuilder workers to check all needed configuration
is present. Designed to be run in a repo where bitbake/oe-core are already present.
This means when we add new autobuilder workers, we can quickly test whether all the needed
funcationality to support the standard yocto project autobuilder (ie. the standard
OE-Core tests) are present.
It uses images prebuilt in a previous release to cut build/testing time.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
Michael Halstead
Richard Purdie