* task is executed even when sstate-cache md5 matches [not found] <1595002721.1496048.1487658650023.ref@mail.yahoo.com> @ 2017-02-21 6:30 ` Pepe Perez 2017-02-22 15:26 ` Richard Purdie 0 siblings, 1 reply; 4+ messages in thread From: Pepe Perez @ 2017-02-21 6:30 UTC (permalink / raw) To: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 478 bytes --] I have following siginfo packages: Generated in my build sstate-cache build/sstate-cache/be/sstate:proc-fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo Previously existing in my build SSTATE_MIRRORS: /central/sstate-cache/be/sstate:proc-fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo I had many other targets where setscene was successful and no task was executed. Why fetch is executed in the target above, if md5 is a match? [-- Attachment #2: Type: text/html, Size: 1245 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: task is executed even when sstate-cache md5 matches 2017-02-21 6:30 ` task is executed even when sstate-cache md5 matches Pepe Perez @ 2017-02-22 15:26 ` Richard Purdie 2017-02-22 16:50 ` Pepe Perez 0 siblings, 1 reply; 4+ messages in thread From: Richard Purdie @ 2017-02-22 15:26 UTC (permalink / raw) To: Pepe Perez, yocto@yoctoproject.org On Tue, 2017-02-21 at 06:30 +0000, Pepe Perez wrote: > I have following siginfo packages: > > Generated in my build sstate-cache > build/sstate-cache/be/sstate:proc- > fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo > > Previously existing in my build SSTATE_MIRRORS: > /central/sstate-cache/be/sstate:proc- > fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo > > I had many other targets where setscene was successful and no task > was executed. Why fetch is executed in the target above, if md5 is a > match? do_fetch is not an sstate task and there is no ".tgz" file, only a siginfo file which is data about how the checksum is constructed and for debugging of other sstate checksums. Pulling the downloads from a download mirror would likely be just as successful as it would be if do_fetch were an sstate task. Cheers, Richard ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: task is executed even when sstate-cache md5 matches 2017-02-22 15:26 ` Richard Purdie @ 2017-02-22 16:50 ` Pepe Perez 2017-02-22 17:10 ` Burton, Ross 0 siblings, 1 reply; 4+ messages in thread From: Pepe Perez @ 2017-02-22 16:50 UTC (permalink / raw) To: Richard Purdie, yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 1625 bytes --] I have however other targets in which do_fetch is not executed at all. Why sometimes is executed and why some others not...?Moreover, I did the test with three users: one populates the sstate-cache, a second resolves its build entirely from sstate and a third one in which do_fetch is executed This is important for me because I'm working in a project in which do_fetch should not be executed, but always resolved with the sstate From: Richard Purdie <richard.purdie@linuxfoundation.org> To: Pepe Perez <pp.perez@yahoo.com>; "yocto@yoctoproject.org" <yocto@yoctoproject.org> Sent: Wednesday, February 22, 2017 7:26 AM Subject: Re: [yocto] task is executed even when sstate-cache md5 matches On Tue, 2017-02-21 at 06:30 +0000, Pepe Perez wrote: > I have following siginfo packages: > > Generated in my build sstate-cache > build/sstate-cache/be/sstate:proc- > fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo > > Previously existing in my build SSTATE_MIRRORS: > /central/sstate-cache/be/sstate:proc- > fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo > > I had many other targets where setscene was successful and no task > was executed. Why fetch is executed in the target above, if md5 is a > match? do_fetch is not an sstate task and there is no ".tgz" file, only a siginfo file which is data about how the checksum is constructed and for debugging of other sstate checksums. Pulling the downloads from a download mirror would likely be just as successful as it would be if do_fetch were an sstate task. Cheers, Richard [-- Attachment #2: Type: text/html, Size: 3614 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: task is executed even when sstate-cache md5 matches 2017-02-22 16:50 ` Pepe Perez @ 2017-02-22 17:10 ` Burton, Ross 0 siblings, 0 replies; 4+ messages in thread From: Burton, Ross @ 2017-02-22 17:10 UTC (permalink / raw) To: Pepe Perez; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 352 bytes --] On 22 February 2017 at 16:50, Pepe Perez <pp.perez@yahoo.com> wrote: > This is important for me because I'm working in a project in which > do_fetch should not be executed, but always resolved with the sstate > do_fetch can't be resolved by sstate. If fetch needs to execute, it will download it from a source mirror or the SRC_URI. Ross [-- Attachment #2: Type: text/html, Size: 780 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-02-22 17:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1595002721.1496048.1487658650023.ref@mail.yahoo.com>
2017-02-21 6:30 ` task is executed even when sstate-cache md5 matches Pepe Perez
2017-02-22 15:26 ` Richard Purdie
2017-02-22 16:50 ` Pepe Perez
2017-02-22 17:10 ` Burton, Ross
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.