Bug 6066

Summary:	toaster_ui.log: "stpd: KeyError saving recipe dependency ..."
Product:	[Build System, Metadata & Runtime] Toaster	Reporter:	David Reyna <david.reyna>
Component:	toaster	Assignee:	Unassigned <unassigned>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Medium	CC:	alexandru.damian, belen.barros.pena, cristiana.voicu, jessica.zhang
Version:	1.6
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description David Reyna 2014-03-29 05:04:57 UTC

I am suddenly seeing these error messages in "toaster_ui.log"

   ...
  stpd: KeyError saving recipe dependency for gnome-desktop-testing, 'virtual/i586-poky-linux-gcc' 
  stpd: KeyError saving recipe dependency for base-passwd, 'virtual/i586-poky-linux-gcc' 

Traceback (most recent call last):
  File "/home/abc/toaster_1_6/poky/bitbake/lib/bb/ui/toasterui.py", line 269, in main
    buildinfohelper.store_dependency_information(event)
  File "/home/abc/toaster_1_6/poky/bitbake/lib/bb/ui/buildinfohelper.py", line 886, in store_dependency_information
    target = tasks[taskdesc]
Exception:   stpd: KeyError saving recipe dependency for busybox, 'virtual/i586-poky-linux-gcc' 
  stpd: KeyError saving recipe dependency for sysvinit, 'virtual/i586-poky-linux-gcc' 
  stpd: KeyError saving recipe dependency for gdbm, 'virtual/i586-poky-linux-gcc' 
  stpd: KeyError saving recipe dependency for elfutils-native, 'virtual/libintl-native' 
  stpd: KeyError saving recipe dependency for gmp, 'virtual/i586-poky-linux-gcc' 
  ...

Comment 1 Alexandru Damian 2014-04-01 11:58:05 UTC

This is a minor error in saving recipe dependencies.

The virtual targets for recipes may not have a corresponding entries in the recipe table, and I preffered to not save bogus entries, but instead not saving the dependencies. 

This happened before, it's just I added an explicit failure message in the toaster log.

Comment 2 Belen Barros Pena 2016-04-25 13:58:55 UTC

This is now fixed: the toaster_ui logs no longer show those errors. It might be related to fixing bug 6169