incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <d...@brondsema.net>
Subject Re: Build failed in Jenkins: Allura #195
Date Tue, 23 Jul 2013 21:22:48 GMT
I think this is an issue with ./run_tests going in parallel and ForgeImporter's
SVN tests conflicting with ForgeSVN's tests on the filesystem.  I had a similar
issue in ForgeUserStats when I first set up run_tests to go in parallel.  The
fix is to have a custom `with_svn` so the same file path isn't used in.

On 7/23/13 5:09 PM, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Allura/195/changes>
> 
> Changes:
> 
> [tvansteenburgh] [#6463] Google Code repo importer
> 
> [tvansteenburgh] [#6463] Encapsulate importer icon
> 
> [tvansteenburgh] [#6463] Add entry point for GC repo importer
> 
> [tvansteenburgh] [#6463] Move get_repo_type() to Extractor and add import guards
> 
> [tvansteenburgh] [#6463] Change svn co url and default mount options
> 
> [tvansteenburgh] [#6487] get fully qualified icon url
> 
> [tvansteenburgh] fixup! [#6487] get fully qualified icon url
> 
> [tvansteenburgh] [#6487] fix license trove names
> 
> [tvansteenburgh] [#6487] handle more complex content-types, e.g. from http://code.google.com/p/msysgit/logo?cct=1342277278
> 
> [tvansteenburgh] [#6487] don't use google code's default icon
> 



-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Mime
View raw message