Hello all,
I think Qi found something. But lets see all points raised one by one:
>
>
>
> This is saying the file on disk with inode 7868999 is:
> WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h
>
> but the pseudo database thinks this is:
>
> WORKDIR/lib32-las/M-WBS0.1-r0/package/usr/src/debug/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h
>
>
> so the question is when was this file created? It would be created by
> do_package since it is in the /package/ directory. It would seem to be
> being deleted outside of pseudo context.
>
>
>
The file is indeed being created by the good execution of the do_package stage.
But on subsequent execution the build fails on do_install.
It is not being deleted outside of pseudo. As I wrote above besides a copy we
do not touch the WORKDIR folder.
Right now I have deleted that build in order to make new builds but the inodes
matched with all those files into WORKDIR since they were hard links.
The strange thing now is that while some executions before the problem was 100%
reproducible now it is not. This is very odd.
>
>
>
> How are you excluding it? I have to wonder if that is somehow breaking
> things due to dependency changes.
>
>
>
I am using:
INHERIT += "rm_work"
RM_WORK_EXCLUDE += "... lib32-las lib32-ldh ..." in local.conf
Since you spoke about dependencies:
ldh recipe depends on las. Both are excluded from rm_work. Sometimes we have
observed the same install issue problem also to ldh recipe.
>
>
>
> Are you saying the first failure is here in the do_install above?
>
>
>
Yes. When I reproduced the error and made my tests.
>
> This is odd. Why would an rm_work run here?
I do not know. I guess it might runs for every recipe and if that recipe is in
RM_WORK_EXCLUDE it just exits?
>
> This is also odd since if rm_work did run, shouldn't the unpack/patch
> need to run again? Didn't you say you'd disabled rm_work for this
> recipe?
I guess that rm_work invocation did not removed anything. Since WORKDIR files
were all there. As wrote above it run and then exists doing nothing since
RM_WORK_EXCLUDE is set.
>
> Something is deleting the files in /package/ which is confusing pseudo.
> The question is what/when. Stepping through this and seeing when the
> files there disappear would be the next step to debug it, narrow down
> when something is deleting them.
>
I am like 99% sure that nothing is touching files outside pseudo. But either
way I will observe the issue and report back in case I find something more and
if reproduced again.
>
>
>
> This is weird since ${S} is usually in PSEUDO_IGNORE_PATHS.
> And if I understand it correctly, if ${S} is in PSEUDO_IGNORE_PATHS,
> pseudo should not complain about any file under ${S}.
> Could you please check if your recipe's PSEUDO_INGORE_PATHS contains
> "WORKDIR/lib32-las/M-WBS0.1-r0/git"?
>
>
>
I checked the PSEUDO_IGNORE_PATHS of the recipe.
S = "${WORKDIR}/git/v2"
So:
PSEUDO_IGNORE_PATHS=".....
WORKDIR/lib32-las/M-WBS0.1-r0/git/v2,
WORKDIR/lib32-las/M-WBS0.1-r0/git/v2"
So as you see the v2 path is into the PSEUDO paths. But the file in question is
one path above and those files are being installed via do_install
install -m 0644 ${WORKDIR}/git/lasiflib/include/* ${D}${includedir}
Would above be the reason somehow? That not the whole ${WORKDIR}/git is not
into PSEUDO?
I could add in PSEUDO_IGNORE_PATHS the S = "${WORKDIR}/git to see if this will
solve the problem.
But first I need to manage to reproduced the error again. Manually right now I
cannot. I will wait till next invocation of our CI.
Regards,
Panagiotis
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59347): https://lists.yoctoproject.org/g/yocto/message/59347
Mute This Topic: https://lists.yoctoproject.org/mt/91650136/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
