| Summary: | Create an autobuilder script to test for long path errors | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Randy MacLeod <randy.macleod> |
| Component: | Scripts and Tools | Assignee: | Sermsity Sunil Kumar Dora <SunilKumar.Dora> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | Deepthi.Hemraj, richard.purdie, ross.burton, sundeep.kokkonda |
| Version: | 2.5 | ||
| Target Milestone: | 6.1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Randy MacLeod
2017-09-14 19:54:16 UTC
I'm not familiar with autobuilder, can anyone do it, please ? Is this something that can be closed? I have not seen any related issue in the recent past ... I am not sure what to do here. Adding a path length test which tested out maximum level supported and maintained that limit would be desirable. The way forward now would be to add a test to qa-extras or qa-extras2 in autobuilder-helper, or maybe add a test to oe-selftest. The open question is how much of the system to test under the max path length and whether its a build from scratch or uses sstate. If its from scratch, it would be quite a long running selftest (although reproducibility does something similar). Bulk move from 4.99 or 0.00 to 5.99 I am working on Implementing a test case under oe-selftest. I will update soon. |