Bug 5603

Summary: regression: Bit bake memres server always reloads the cache
Product: [Build System, Metadata & Runtime] BitBake Reporter: Jason Wessel <jason.wessel>
Component: bitbakeAssignee: Alexandru Damian <alexandru.damian>
Status: VERIFIED NOTABUG QA Contact: Mihail Stanciu <stanciux.mihail>
Severity: normal    
Priority: Medium+ CC: alexandru.c.georgescu, alexandru.damian, corneliux.stoicescu, cristiana.voicu, jessica.zhang, poky.bs.watcher, poky.watcher, richard.purdie
Version: 1.7   
Target Milestone: 1.7   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 5535    

Description Jason Wessel 2013-11-26 16:03:29 UTC
A regression was introduced with commit:

===
commit dd15648fc2654b8d7c3e00ea7ab3dbf04f24f24b
Date:   Fri Sep 13 17:32:53 2013 +0100

    cooker/command: Add finishcommand to reset cooker state
    
    After running a command on the server, it needs to reset to the initial
    state. This ensures that subsequent clients start from a known state
    and notice any configuration changes.
    
    Ultimately we may want to do more than this buts a good start and better
    than nothing.
===

The test is to run an operation twice where we expect that the cache should not reload or that the reload operation is extremely fast, vs a full cache reload. 

. oe-init-build-env-memres
bitbake -c patch bash
# Now there should be no cache reload on the second try
bitbake -c patch bash
Comment 1 Cristiana Voicu 2014-03-26 08:05:26 UTC
patch sent to bitbake ml
Comment 2 Cristiana Voicu 2014-03-26 08:06:53 UTC
Removed 5535 from depends, because after investigation I found that there is a different issue. For #5535, the server should always be reseted, but for the current issue a sanity check for the cache is needed.
Comment 3 Alexandru Damian 2014-03-28 11:40:31 UTC
IMHO, this is not a bug, but an expected behaviour, see bug 5535.
My point is that bug 5535 is in direct conflict with this bug, and 

I would expect a cooker reset and a full cache reload between build commands. The bitbake server should reload the configuration files and recipe caches between builds, since they may have changed.

I think we need to revise this test.
Comment 4 Alexandru Damian 2014-10-28 10:43:13 UTC
Not a bug as per above comments.
Comment 5 Mihail Stanciu 2015-01-22 13:08:19 UTC
Verified on master: d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b

Does not need TC, will be covered in TC for bug 6935