[OE-core] [PATCH 11/11] oe-selftest: add a test for upstream version check regressions
Alexander Kanavin
alexander.kanavin at linux.intel.com
Mon Apr 24 12:20:58 UTC 2017
On 04/23/2017 10:57 PM, Burton, Ross wrote:
> The test runs an upstream version check, and then compares the
> list of recipes that failed the check (i.e. those where latest
> upstream version could not be established) against the list of
> known-broken upstreams. Mismatches either way (upstream check failed,
> recipe not in the exception list, or upstream check worked,
> recipe in exception list) fail the test.
>
>
> This fails on the autobuilder:
> The following packages failed upstream version checks. Please fix them
> using UPSTREAM_CHECK_URI/UPSTREAM_CHECK_REGEX
> (when using tarballs) or UPSTREAM_CHECK_GITTAGREGEX (when using git). If
> an upstream version check cannot be performed
> (for example, if upstream does not use git tags), you can add the
> package to list of exceptions in
> meta-selftest/files/distrodata/checkpkg_exceptions.
> kmscube
New recipe that is not yet in master, does not have version tags.
> bmap-tools
> libcap-ng
These two work ok on my local machine :-/ Let's see if this was a
one-off glitch.
> boost
Upstream check got broken with update to 1.64.0, will fix.
> The following packages have been checked successfully for upstream
> versions (or they no longer exist in oe-core),
> but are in the exceptions list in
> meta-selftest/files/distrodata/checkpkg_exceptions. Please remove them
> from that list.
> x264
Needs 'commercial' whitelisting in configuration, will fix.
I'll send an updated patch.
Alex
More information about the Openembedded-core
mailing list