It's an issue with a recipe in your custom layer. If you can show the layer, we may be able to help.
Are you sure a current timestamp isn't sneaked into the build by something in that layer? Alex On Thu, 20 Feb 2020 at 17:03, Dmitri Toubelis < [email protected]> wrote: > Hi, > > I'm migrating from yocto morty to zeus and I'm receiving a whole lot of > errors like this: > > ERROR: When reparsing > /srv/yocto/poky/meta-loopedge/meta-loopedge-dist/recipes-core/images/loopedge-std.bb:do_image_wic, > the basehash value changed from > 8dd96e09d0b7defa552e586e626933ca37ace5180918ea65addbfcb6c1247b1c to > e38fae3f400b3e3de114fcd668d46a1f7c3eec436ec72962e78df906714a6fb0. The > metadata is not deterministic and this needs to be fixed. > ERROR: The following commands may help: > ERROR: $ bitbake loopedge-std -cdo_image_wic -Snone > ERROR: Then: > ERROR: $ bitbake loopedge-std -cdo_image_wic -Sprintdiff > > ERROR: When reparsing > /srv/yocto/poky/meta-loopedge/meta-loopedge-dist/recipes-core/images/loopedge-std.bb:do_image_ext4, > the basehash value changed from > a8209ab35324ce59bb193b80871c12c492f69f42fd97b03801165bd4a12670f6 to > 1ab2d25ef217fe87b4cce1106d122acd4286043b04dcd74d98df30a01aa6a0b9. The > metadata is not deterministic and this needs to be fixed. > ERROR: The following commands may help: > ERROR: $ bitbake loopedge-std -cdo_image_ext4 -Snone > ERROR: Then: > ERROR: $ bitbake loopedge-std -cdo_image_ext4 -Sprintdiff > > ERROR: When reparsing > /srv/yocto/poky/meta-loopedge/meta-loopedge-dist/recipes-core/images/loopedge-std.bb:do_image_tar, > the basehash value changed from > c5ab62cac832e502a338d59124efc690e66560a4e877bc4ba3487c3a734c2497 to > bb7ca72863614cb5c9915eb502259b1ffa8b98992f7ad3280d1e049a1824b930. The > metadata is not deterministic and this needs to be fixed. > ERROR: The following commands may help: > ERROR: $ bitbake loopedge-std -cdo_image_tar -Snone > ERROR: Then: > ERROR: $ bitbake loopedge-std -cdo_image_tar -Sprintdiff > > I search around for answers and there are here are reasons and solutions > for this that I found: > - to make sure any date related variables are excluded from basehash via > `do_task_name[vardepsexclude] = "DATE DATETIME"` > - clears state cache with `bitbake image -c cleansstate` > - delete tmp directory and build from scratch > > Here is my observation and interpretation: > - this messages occur when running with pristine build directory, i.e. it > only contains 2 files in `conf` dir - `local.conf` and `bblatyers.conf`, so > I can rule out contamination from a previous run. > - same messages reapeat over and over totalling ~900 errors at the end of > the run > - I have few custom classes and I removed them from the image to rule out > contamination from my own code. > - Tasks that give this error are coming from image.bbclass from poky and > none of them have been altered in any way. > - The image build runs through the end but because bitbake exits with > non-zero exit code it breaks lots of our tools, so just ignoring them is a > bad option. > > So, am I doing something obviously wrong? It is a known issue in zeus? And > if so is there a known workaround? > > Thanks in advance. > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48537): https://lists.yoctoproject.org/g/yocto/message/48537 Mute This Topic: https://lists.yoctoproject.org/mt/71431201/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
