Bug 11896

Summary:	checkpkg needs to have exemption in metadata
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Ross Burton <ross.burton>
Component:	devtools / tool chain	Assignee:	Alexander Kanavin <alex.kanavin>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	meta.mr.watcher, meta.watcher
Version:	2.4
Target Milestone:	2.4 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Ross Burton 2017-08-04 09:51:29 UTC

The checkpkg selftest has to maintain a separate list of recipes that can't pass checkpkg's upgrade testing.  This isn't scalable to other layers as there is only a single exception list.

The checkpkg logic should have a variable that recipes can set to exclude themselves from the upgrade check.  This will speed up checkpkg, and allow tooling to tell between "couldn't tell if there is an upgrade" and "we cannot tell if there is an upgrade" (where the former could be fixed or be transient network failure).

Comment 1 Alexander Kanavin 2017-08-07 10:23:51 UTC

I think there is a need for two per-recipe variables actually:

UPSTREAM_CHECK_UNKNOWN - set if the upstream check fails reliably, e.g. absent git tags, or weird versions used on our or on upstream side. The upstream check test will treat this the same way it treats the exception list now - mismatches both ways will be reported as failures.

UPSTREAM_CHECK_UNRELIABLE - set if the upstream check cannot be reliably performed due to transient network failures, or server behaving weirdly. This one should be used sparingly, as it completely excludes a recipe from upstream checking. The upstream check test will never fail.


Agree?

Comment 2 Ross Burton 2017-08-09 10:55:45 UTC

That seems reasonable, yes.