On Mon, 10 Apr 2023 at 17:32, Jose Quaresma <[email protected]> wrote:
> Hi Frederic, > > Frederic Martinsons <[email protected]> escreveu no dia > domingo, 9/04/2023 à(s) 16:05: > >> >> >> Le dim. 9 avr. 2023, 10:43, Richard Purdie < >> [email protected]> a écrit : >> >>> On Sat, 2023-04-08 at 09:56 +0200, Frederic Martinsons wrote: >>> > Forget my previous question, >>> > >>> > I simply >>> > edit https://git.openembedded.org/openembedded-core/tree/meta/lib/oeq >>> > a/selftest/cases/reproducible.py#n137 >>> > to replace by zavariant, and with OEQA_DEBUGGING_SAVED_OUTPUT set , I >>> > managed to see the html diff >>> > >>> > Nevertheless, It took one hour, but it seems that it cannot be >>> > avoided since there are two builds and one >>> > without any shared state. >>> >>> Unfortunately that is the nature of the test, one side has to be built >>> from scratch. Tweaking the test as you'd done to target a specific >>> component is what I'd have done too to speed things up for a specific >>> recipe. >>> >>> To get a further speedup, you could probably keep the sstate for each >>> of the two builds separate but retain both, then in theory on the >>> pieces you change would rebuild. Again, it would mean tweaking the test >>> but for debugging, I think that is fine. Rust can be a pain if you just >>> rebuild those as it still takes a while. Thanks for taking a look! >>> >>> Cheers, >>> >>> Richard >>> >>> >> Thank you for the tip, I'll try that, everything that help to speed up is >> good to take of course. >> > > To speedup the build you can take the rust-native from the state cache [1] > and this will improve a bit bit the time needed: > > sstate_target = [ "rust-native" ] > > [1] > https://git.openembedded.org/openembedded-core/tree/meta/lib/oeqa/selftest/cases/reproducible.py#n139 > > > Jose > > >> >> >> >> > > -- > Best regards, > > José Quaresma > Hey, thank you José for the advice, I'll apply that for sure. By the way, like I commented in https://bugzilla.yoctoproject.org/show_bug.cgi?id=15090 , I'm currently try to reproduce (ahah) the reproducibility issue of zvariant with the use of reprotest (https://salsa.debian.org/reproducible-builds/reprotest) and outside yocto environment. For the moment, I was not able to pinpoint the issue (I must have put aside the faketime usage since it caused me segfault of rustc). I plan to dig further in reproducible.py class and how the package is built under yocto to try to find out what is going on.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#179892): https://lists.openembedded.org/g/openembedded-core/message/179892 Mute This Topic: https://lists.openembedded.org/mt/98126404/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
