Created attachment 2168 [details] toaster_db Hi, There are a lots of fields that are always empty in the toaster db. BUILD: 1.7_M4.RC3: 5367855fe56db0c09b8fa7bb423b9de18d11eecc orm_recipe_dependency dep_type 0 orm_variable changed 0 orm_variable human_readable_name "" orm_logmessage task_id None orm_task work_directory "" orm_task line_number 0 orm_task source_url "" orm_target image_size 0 orm_helptext area 0 orm_variablehistory value "" orm_recipe up_date None orm_recipe up_id None Attached the DB. Cheers, Ionut C
Ionut, can you give some information on what configuration you used to generate this build and what the initial state was before the build?
Hi Paul, That was a normal non managed mode build for toaster. To reproduce: 1. Clone poky; 2. source env 3. source toaster start 4. bitbake core-image-minimal For getting those results there is a script which selects all the tables from the toaster db and for each table, it is selecting all the rows having null or empty values. Please let me know if you want more infos. Cheers, Ionut C
It is normal for to have empty fields across all rows in the database, especially when using the 1.7 database format for running 1.6-mode builds, e.g. up_* fields get populated only by 1.7 code. Furthermore, the default value is a valid value for that field, e.g. orm_recipe_dependency dep_type should be 0 at all times, because we collect direct relationship dependencies, and infer the reverse dependencies. Some of the fields we don't collect at all, and are not used for the interface, but they are there to allow for further enhancements that have been planned but not executed, e.g. orm_variable changed, human_readable_name fields. Close this report as Not a bug; if reopened, it would be very helpful to me to pinpoint a single mis-recorded variable, an a specific scenario on where the variable should be recorded and it is not recorded, or it is recorded with a value that is not the expected value.