Bug 1480 - [HOB] Could not trigger another build after stop build
Summary: [HOB] Could not trigger another build after stop build
Status: VERIFIED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1
Assignee: Joshua Lock - Disabled
QA Contact:
URL: Patch submitted
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-09-14 01:08 UTC by Jiajun Xu
Modified: 2011-09-26 23:11 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiajun Xu 2011-09-14 01:08:24 UTC 
tree/branch: poky/master
commit: ce66e2c6bd117d1a40b547b10b376524f9276d16

With latest master, if I start a build and force stop it then trigger another new build, nothing will be built out.

BTW, if I wait for the first build finished, the second build will have no such issue.
Comment 1 Joshua Lock - Disabled 2011-09-14 09:12:44 UTC 
Can you be more explicit here? What do you mean by nothing will be built? Do you see error messages in the GUI or on the console?

I'm trying to reproduce but it'd be nice to have more information to go on.

Thanks
Comment 2 Joshua Lock - Disabled 2011-09-14 16:27:08 UTC 
After several tries I am able to Force Stop and begin another build.

We do warn in the Force Stop confirmation dialog:

"'Force Stop' will stop the build as quickly as possible but may well leave
your build directory in an  unusable state that requires manual steps to fix."

This will often be the case if the 'Force Stop' is in the middle of a
compilation process, it is unlikely that the mid-compilation package will be
able to be built again without first cleaning it.

Or are you seeing something altogether different?

Do we need to change 'Force Stop' to 'Force Stop and Exit" ?
Comment 3 Joshua Lock - Disabled 2011-09-14 17:38:40 UTC 
After discussion with Jiajun it seems this issue was discovered whilst doing a packages only build.
Comment 4 Joshua Lock - Disabled 2011-09-15 15:33:06 UTC 
I am able to reproduce this issue by running a packages only build, using 'Force Stop', then attempting the same packages only build again (in this instance, acl).

I see the following backtrace on the CLI:
"
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 530, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 483, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/joshual/Projects/Yocto/poky/bitbake/lib/bb/cache.py", line 597, in sync
    for key, info_array in self.depends_cache.iteritems():
AttributeError: 'Cache' object has no attribute 'depends_cache'
"
Comment 6 Jiajun Xu 2011-09-26 23:11:34 UTC 
Verify the bug as fixed with edison branch.