<?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>1659</bug_id>
          
          <creation_ts>2011-10-05 12:12:12 +0000</creation_ts>
          <short_desc>[Usability] Way to determine what is about to happen (similar to a dry-run)</short_desc>
          <delta_ts>2013-04-30 10:14:27 +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>OE-Core</product>
          <component>devtools / tool chain</component>
          <version>1.4</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>1.4 M5</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Mark Hatle">mark.hatle</reporter>
          <assigned_to name="Robert Yang">liezhi.yang</assigned_to>
          <cc>corneliux.stoicescu</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>liezhi.yang</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
    
    <cc>song.liu</cc>
    
    <cc>zhenfeng.zhao</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>16733</commentid>
    <comment_count>0</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2011-10-05 12:12:12 +0000</bug_when>
    <thetext>When updating a recipe, or doing a git pull from upstream.  It would be nice to be able to run a command that would evaluate the recipes, use the checksumming, stamps, etc and tell me what is about to run, and why.

This way I can do a pull and if eglibc changed, causing every package in the system to rebuild -- I may simply revert and delay my update to later.

If I&apos;m debugging something and trying to understand if I change libnl, why suddenly 30% of the system is rebuilding -- it might give me a list of things I need to verify still work properly after a build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20954</commentid>
    <comment_count>1</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2012-05-01 17:19:38 +0000</bug_when>
    <thetext>Is -n what your looking for?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20995</commentid>
    <comment_count>2</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2012-05-02 16:29:15 +0000</bug_when>
    <thetext>-n does not appear to be what I am referring to.

-n will simply do a dry run and tell you what is going to happen, but it won&apos;t tell you why.

What I&apos;d like to see is an argument that will say:

do_fetch, run because version/pr changed

do_patch, run because SRC_URI references changed

do_compile, run because chksum of do_compile changed


That way when you do a git pull (or bring in a layer, or...) you can run a command and figure out what is going to happen, and why it&apos;s going to happen.. this will let you see if you really want to do it -- or if you are trying to figure out why each time you build some task keeps executing, when you don&apos;t think it should.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23514</commentid>
    <comment_count>3</comment_count>
    <who name="Robert Yang">liezhi.yang</who>
    <bug_when>2012-07-26 08:13:18 +0000</bug_when>
    <thetext>Hi Richard,

I re-routed this feature to the &quot;Product: Bitbake&quot;, would you please help me to take a look at the design? (The Queues in bitbake/lib/bb/runqueue.py are so complicated).

Here is the design doc:

1) This is similar to &quot;bitbake -n&quot;, I think that we don&apos;t have to add a new option, just make an improvement to the &quot;bitbake -n&quot; is OK, the &quot;bitbake -n&quot; goes through the motions, and show a summary in the end currently (e.g.: bitbake -n core-image-sato):

NOTE: Running noexec task 5459 of 5459 (ID: 10, /buildarea2/lyang1/poky/meta/recipes-sato/images/core-image-sato.bb, do_build)
NOTE: Tasks Summary: Attempted 5459 tasks of which 5457 didn&apos;t need to be rerun and all succeeded.

We can the print why it needs to re-run, e.g.:
NOTE: (/buildarea2/lyang1/poky/meta/recipes-sato/images/core-image-sato.bb, do_build) needs re-run xxx

2) Edit check_stamp_task or add a similar function to return the reason why need re-run, and print the it when dry-run (-n)

3) The message will be printed by logger.info in lib/bb/runqueue.py</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>23516</commentid>
    <comment_count>4</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2012-07-26 08:55:48 +0000</bug_when>
    <thetext>I&apos;m going to aim a bit higher here and propose a bitbake-whatchanged script. This would basically:

a) run something like STAMPS=/some/tempdir bitbake xxx -S

This would generate the siginfo files for what bitbake xxx would build (without actually building it).

b) Compare the output in /some/tempdir with that in STAMPS and the hashes availble in the sstate cache.

The default output would probably be something like a count of the recipes that would be built, a count of those installed from sstate and count of things that are unchanged.

Extra parameters to bitbake-whatchanged would allow you to dive into the details of why any given thing was getting rebuilt, down to providing the output of bitbake-diffisgs against the appropriate files.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>24066</commentid>
    <comment_count>5</comment_count>
    <who name="Robert Yang">liezhi.yang</who>
    <bug_when>2012-08-15 15:36:49 +0000</bug_when>
    <thetext>Re-route it to oe-core since it will go into oe-core/scripts/</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>25562</commentid>
    <comment_count>6</comment_count>
    <who name="Robert Yang">liezhi.yang</who>
    <bug_when>2012-09-24 06:50:12 +0000</bug_when>
    <thetext>Move it to 1.4 since the name of the nativesdk changed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30552</commentid>
    <comment_count>7</comment_count>
    <who name="Robert Yang">liezhi.yang</who>
    <bug_when>2013-03-08 01:21:50 +0000</bug_when>
    <thetext>Merged:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1e6d0da8d5456d04c2354d37900a59d292bcd898

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4d5ef2af504635c60ffd2d971191bc111035c3a2</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>31026</commentid>
    <comment_count>8</comment_count>
    <who name="Stoicescu Cornel">corneliux.stoicescu</who>
    <bug_when>2013-03-22 11:06:19 +0000</bug_when>
    <thetext>Verified in master:9ffee9add2d0380f4025e7a678a166f25a7d659e

Test steps:
1) &quot;bitbake man&quot;
2) add &quot;x11vnc&quot; to &quot;DEPENDS&quot; in &quot;meta/recipes-extended/man/man_1.6g.bb&quot;
3) &quot;bitbake-whatchanged -v man&quot;

Result: Output describes what needs to be done/redone over the previous man build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32758</commentid>
    <comment_count>9</comment_count>
    <who name="Stoicescu Cornel">corneliux.stoicescu</who>
    <bug_when>2013-04-30 10:14:27 +0000</bug_when>
    <thetext>test case created: https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=754</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>