10149 2016-08-15 23:31:00 +0000 Crash in image.bbclass 2016-08-29 00:32:10 +0000 1 1 7 Build System, Metadata & Runtime OE-Core deployment 2.2 x86 Multiple RESOLVED FIXED Medium+ normal 2.2 M3 1 mark.hatle bluelightning sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 65211 0 mark.hatle 2016-08-15 23:31:00 +0000 Using the configuration: IMAGE_INSTALL_append = " packagegroup-core-buildessential" EXTRA_IMAGE_FEATURES_append = " dev-pkgs" MACHINE='qemux86' bitbake core-image-base bitbake -c clean gobject-introspection bitbake core-image-base This results in: ERROR: core-image-base-1.0-r0 do_rootfs: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: <module> 0001: *** 0002:do_rootfs(d) 0003: File: '/home/mhatle/git/oss/oe-core/meta/classes/image.bbclass', lineno: 209, function: do_rootfs 0205: # the weightings as well as a map to the lines where next_stage() was 0206: # called. Of course this isn't critical, but it helps to keep the progress 0207: # reporting accurate. 0208: stage_weights = [1, 203, 354, 186, 65, 4228, 1, 353, 49, 330, 382, 23, 1] *** 0209: progress_reporter = bb.progress.MultiStageProgressReporter(d, stage_weights) 0210: progress_reporter.next_stage() 0211: 0212: # Handle package exclusions 0213: excl_pkgs = d.getVar("PACKAGE_EXCLUDE", True).split() Exception: AttributeError: 'module' object has no attribute 'progress' ERROR: core-image-base-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/mhatle/git/oss/oe-core/build/tmp-glibc/work/qemux86-oe-linux/core-image-base/1.0-r0/temp/log.do_rootfs.122391 65500 1 bluelightning 2016-08-25 01:06:34 +0000 Mark, which version of bitbake are you using here? Is it perhaps one before the progress reporting code was added? 65502 2 mark.hatle 2016-08-25 13:28:05 +0000 This was master on August 15th. 65574 3 bluelightning 2016-08-28 23:42:42 +0000 So far I've been unable to reproduce this. Do you definitely have a bitbake/lib/bb/progress.py ? 65577 4 mark.hatle 2016-08-29 00:32:10 +0000 I did at the time. I had verified that. It was a very very strange error. I have attempted to reproduce the problem with the latest master (bitbake and oe-core) with the same build as previous. The problem did not reappear. I'd say it must have been fixed in an unrelated change. Setting as resolved.