<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>1480</bug_id>
          
          <creation_ts>2011-09-14 01:08:24 +0000</creation_ts>
          <short_desc>[HOB] Could not trigger another build after stop build</short_desc>
          <delta_ts>2011-09-26 23:11:34 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Hob</product>
          <component>hob</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc>Patch submitted</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.1</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jiajun Xu">jiajun.xu</reporter>
          <assigned_to name="Joshua Lock - Disabled">josh</assigned_to>
          <cc>jessica.zhang</cc>
    
    <cc>jiajun.xu</cc>
    
    <cc>ke.yu</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>sgw</cc>
    
    <cc>wenhuax.fan</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>16167</commentid>
    <comment_count>0</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2011-09-14 01:08:24 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16179</commentid>
    <comment_count>1</comment_count>
    <who name="Joshua Lock - Disabled">josh</who>
    <bug_when>2011-09-14 09:12:44 +0000</bug_when>
    <thetext>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&apos;m trying to reproduce but it&apos;d be nice to have more information to go on.

Thanks</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16199</commentid>
    <comment_count>2</comment_count>
    <who name="Joshua Lock - Disabled">josh</who>
    <bug_when>2011-09-14 16:27:08 +0000</bug_when>
    <thetext>After several tries I am able to Force Stop and begin another build.

We do warn in the Force Stop confirmation dialog:

&quot;&apos;Force Stop&apos; 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.&quot;

This will often be the case if the &apos;Force Stop&apos; 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 &apos;Force Stop&apos; to &apos;Force Stop and Exit&quot; ?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16200</commentid>
    <comment_count>3</comment_count>
    <who name="Joshua Lock - Disabled">josh</who>
    <bug_when>2011-09-14 17:38:40 +0000</bug_when>
    <thetext>After discussion with Jiajun it seems this issue was discovered whilst doing a packages only build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16231</commentid>
    <comment_count>4</comment_count>
    <who name="Joshua Lock - Disabled">josh</who>
    <bug_when>2011-09-15 15:33:06 +0000</bug_when>
    <thetext>I am able to reproduce this issue by running a packages only build, using &apos;Force Stop&apos;, then attempting the same packages only build again (in this instance, acl).

I see the following backtrace on the CLI:
&quot;
Exception in thread Thread-5:
Traceback (most recent call last):
  File &quot;/usr/lib/python2.7/threading.py&quot;, line 530, in __bootstrap_inner
    self.run()
  File &quot;/usr/lib/python2.7/threading.py&quot;, line 483, in run
    self.__target(*self.__args, **self.__kwargs)
  File &quot;/home/joshual/Projects/Yocto/poky/bitbake/lib/bb/cache.py&quot;, line 597, in sync
    for key, info_array in self.depends_cache.iteritems():
AttributeError: &apos;Cache&apos; object has no attribute &apos;depends_cache&apos;
&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16336</commentid>
    <comment_count>5</comment_count>
    <who name="Joshua Lock - Disabled">josh</who>
    <bug_when>2011-09-20 15:17:28 +0000</bug_when>
    <thetext>http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=081990b2a3d27c83f17d79265d0c77271e9d6638</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>16507</commentid>
    <comment_count>6</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2011-09-26 23:11:34 +0000</bug_when>
    <thetext>Verify the bug as fixed with edison branch.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>