Currently, the multiple clones are taking quite a long time (11-12 seconds each for core, meaning up to 30 seconds per test)

DamZ suggests we keep a local repository, created on demand, updated occasionally, as a cache.

1. If reference repo doesn't exist, create it
2. Use git clone --reference when cloning
3. Add a cron or something which will update reference repos periodically

CommentFileSizeAuthor
#1 pifr.reference_repository.patch3.38 KBrfay

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Needs review
StatusFileSize
new pifr.reference_repository.patch3.38 KB

I used a very simple technique here - just a variable that, if set, lets us use a reference, and if that's set, it changes the clone.

I get clones of Drupal in 3-4 seconds using this technique, and updating the reference repo takes no time at all.

My plan is to incorporate the management of the reference repo into the testbot puppet package cron. So PIFR just *uses* the reference repo if available, it doesn't manage it.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Needs review » Fixed

Committed: http://drupal.org/cvs?commit=502822

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.