We would like to check that oe-core can build with very long project path lengths. This should be automated and run periodically to check for regressions. The test would need to be a full source build rather than use sstate to be effective and that might be a problem for the YP build farm usage. Rather than doing 10s of builds to binary search for the exact maximum path length, we could manually determine and fix the code to adhere to a 'reasonable' long path length of say 2-400 characters, then just look for regressions from that value. Then we could work on increasing the limit if needed. I think it makes sense to run a check every day to pick up changed packages using sstate, then run a ~weekly test that does not use sstate. related defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6986
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.