Since we now have functional buildhistory repository functionality,
generate buildhistory-diff output for builds where its enabled.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently there was no way to override an existing extra vars
assignment, which meant BB_NUMBER_THREADS was impossible to change.
This adds code to allow the higher override of a value to override
the other settings which makes the code function more as a user
would expect.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently it was being placed a directory level too high and hence
was being ignored.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ensures that release branch performance build tests work on the correct
branch and that comparisions between mut+master and master-next+master
start to work correctly. It also ensures reports for the current
revision are generated even if later revisions are built.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The shell script can't access the config.json data easily, convert
from shell to python so that we prepare the way for further enhancements.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This makes the build performance code behave similarly to the other
results publishing code using the standard location.
Also tweak the report names so they sort.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need the final logging to show which command steps contain errors so print
failing commands but allow the code to continue and show the final log output.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ensures the builds get as far as they can when there is failure rather
that stopping at the first sign of one. This means caches are hotter and
allows for faster respins, at the cost of the failure being lost in longer
logs.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This should further protect us against contamination between different build directories
as old build directory paths should no longer exist.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is no current mechanism to reference the 'builddir' within the config.json,
so add HELPERBUILDDIR for this purpose.
Use this to set SSTATEDIR for nightly-bringup, meaning sstate arefacts should be
shared for use between the different oe-selftest threads, speeding up builds.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The SSTATEDIR was accidentally using getconfiglist instead of getconfigvar which
meant it couldn't be unset. Fix to use var so the values in config.json work
as intended.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Many of the distros we use have sendmail in /sbin or /usr/sbin
which may not be in the path for non-interactive users. Handle
this in the script to avoid failures where tests work but the
real QA email fails.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add in the support to publish images into the designated path.
BSP packages of the previous build will be cleaned up before
new BSP packages are copied over. This ensures the previous
image will not be retained and causes conflicts before image
is loaded into x86_64 (MTURBOT64) hardware.
Signed-off-by: Aaron Chan <aaron.chun.yew.chan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[RP: Minor tweaks made to adpat to buildbot and option naming
Fixed shared-repo-unpack for publishing when no cache-dir supplied]
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new buildbot code can directly monitor the logfiles itself so
we need to be able to optionally stop echoing onto the console.
Add missing flush() calls and print the command being used and logfile
so its clear what is happening on stdout too.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
