distutil warnings are causing CI to fail. This is caused by changes
outside of meta-arm, and are not relevant for anything present in
meta-arm. Temporarily ignore these until they can be handled upstream.
Signed-off-by: Jon Mason <jon.mason@arm.com>
SourceForge in particular doesn't like multiple connections from the
same IP, but when a source mirror is being populated for the first time
this will happen. Our fetch falls back to the Yocto mirror so it doesn't
cause a failure, but there is a warning logged which our CI then fails
because of.
As we don't care about these warnings, filter them out of the log before
checking if there were any errors.
Change-Id: I36c97c5d9923f1c4d14c4588f3780211cccb57b2
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
The files in kas/ are not generic Kas files, but instead designed
specifically and solely around the CI system.
Change-Id: I30082392ad2231a4c1c41e54a292595adf81715b
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
Jon Mason
Ross Burton