| Summary: | YoctoProject Compatibility script improvements needed | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Armin Kuster <akuster> |
| Component: | Scripts and Tools | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | akuster808, antonin.godard, mathieu.dubois-briand, mingli.yu, ndec13, randy.macleod, richard.purdie, ross.burton, tgamblin |
| Version: | 0.0.0 | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Armin Kuster
2019-04-16 16:02:25 UTC
one more. w & w/o ptest. this is the one that breaks meta-oe. The issue at hand is if layer D depends on B & C and neither of those pass, the Layer D can not pass. If that is a hard fast rule, what is the point of such a rule? Also, it limits the number of applicants. I have not done anything with this. Didn't the TSC discuss this and clarify the creteria? Also, the autobuilder now does run tests automatically for some layers and Nico and others did improve the script? Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team. Moved to M4. Bulk move to 5.0 M1. -- Randy Bulk move of 52 5.0-M1 bugs to M2. Writing down thoughts here because it's better than nowhere: - replacing core classes is a hard no Things which are dubious but right now the test is a hard yes/no and there are exceptional circumstances we want to allow, so these will have to wait until there's an exception process: - enabling networking in compile - extra hosttools Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3. Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone. We have somewhat improved docs: https://docs.yoctoproject.org/test-manual/yocto-project-compatible.html and this page has been improved: https://www.yoctoproject.org/compatible-registration/ but we haven't been quite as detailed as requested in this bug report. Antonin, Mathieu, I'm CCing you for docs and layer compatibility checking point of view. Should the script and docs be more explicit ? |