bugTest-AutoBuild - Bugs: bug #8020, Cached builds fail

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #8020: Cached builds fail

Submitted by:  Marcus Hardt <marcus>
Submitted on:  Thu 14 Dec 2006 10:24:45 AM UTC  
 
Category: Test-AutoBuildSeverity: 3 - Normal
Priority: 5 - NormalStatus: None
Privacy: PublicAssigned to: None
Open/Closed: OpenRelease: None

Fri 15 Dec 2006 09:32:07 PM UTC, comment #5:

Ok, that's good news - thanks for the update. I'll put a note about this issue into the FAQ / troubleshooting section too.

Daniel Berrange <danpb>
Project Administrator
Fri 15 Dec 2006 03:40:26 PM UTC, comment #4:

Well, it's solved, already.

The 23MB were seen during another build. The build finished with just above 100MB, thus the cache ran full.

Maybe this deserves a note in the autobuild.log file.

Thanks a lot for helping!!!

Marcus Hardt <marcus>
Fri 15 Dec 2006 03:26:00 PM UTC, comment #3:

Ahh, I understand now. Can you run a cycle passing the '--debug' command line flag. This will generate a huge amount of logging info on stdout - save that to a file & attach it to this ticket. This log info should contain data about why it is not using the cached builds.

Daniel Berrange <danpb>
Project Administrator
Fri 15 Dec 2006 02:52:51 PM UTC, comment #2:

There was nothing failing. It's just not using cached builds, once I add the module "crossbroker" to the list of modules.

There is only one dir:
/var/lib/builder/build-archive/1166189222
it is 23M of size, however, I'll try setting cachesize to 1000MB.

However, I'm afraid this won't help. I suspect the module writing to some directory that it isn't allowed to. I'll monitory this dir.

Marcus Hardt <marcus>
Thu 14 Dec 2006 05:56:03 PM UTC, comment #1:

Autobuild will always save the result of a successfull module build in the cache. On the next build cycle, the cache will only be used if there were no new changes in the source repository for the module, or any modules it depends on.

What sort of failure did you see when using the cache ? Did the autobuild engine itself crash, or just the compile/build process of a module failing ?

How large is a single cached build archive under /var/lib/builder/build-archive/XXXXXXX ? The default config limits cache size to 100 MB, so perhaps the output of your set of modules is exceeding 100 MB & autobuild isn't dealing with this correctly. If so, try increasing the size limit to be 'n' times the expected build output size. eg, if a single archive is 300 MB, then setting the maxCacheSize to 900 MB would allow 3 historic cached build.

Daniel Berrange <danpb>
Project Administrator
Thu 14 Dec 2006 10:24:45 AM UTC, original submission:

Hi,

I've a strange problem with cached builds. They stop working for all modules when I add one more module. Cached builds used to work fine - even with the specific module that caused the problem.

It seems that the developer just had to add two more RPMs to build to change it for bad.

How does autobuild detect wether or not to cache a build for a module.

If you want to check: it's the crossbroker module at http://savannah.fzk.de/autobuild

Best,
Marcus.

Marcus Hardt <marcus>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by danpb (Posted a comment)
  • -unavailable- added by marcus (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup