Using a custom logging.yml we can instruct BitBake's logger to write all
warnings and errors into a separate log file.
Then after the build has finished we can see if the log file is empty and if
not show it and abort the build.
Change-Id: Ida835b5c822941fb513dfb1758b4ec195e0050fc
Signed-off-by: Ross Burton <ross.burton@arm.com>
Simplify the gitlab-ci by having the bootstrap build as just another Kas
overlay file, so there's no duplication of build script.
Change-Id: I7341750d2ae7f3c146bfe323f61fa98c0f3121c0
Signed-off-by: Ross Burton <ross.burton@arm.com>
Add kas scripts that generic to test builds, and a GitLab CI runner.
This is mainly a cut-down copy of what is in the master/gatesgarth
branches with the following changes:
- Just the BSPs that are in the Dunfell release, obviously
- No clang testing. There are patches in master that can be backported
if required.
- Added testing of the armgcc-9.2 compiler. This is currently broken for
some configurations in master and the testing will be forward-ported
when it passes.
Change-Id: I9c2a4f66318b3ccc066d423f3533202ee33f0c9d
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Ross Burton
Ross Burton