From thewoolleyman at gmail.com  Wed Nov 12 15:28:30 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 12 Nov 2008 13:28:30 -0700
Subject: [Cruisecontrolrb-developers] Git project building over and over
	even though there are no commits
Message-ID: <e3af97510811121228g420a147fq3e63c9d8e0893776@mail.gmail.com>

Updating to latest ccrb trunk didn't help, restarting cruise/box didn't work
- it just builds every 5 minutes.  Working copy looks clean.

Anyone seen this?

This is on the new Rails CI server, if anyone wants to help debug it I can
give access.  I don't have time right now, waiting to see if it goes away on
the next commit.

-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081112/66fa0945/attachment.html>

From thewoolleyman at gmail.com  Wed Nov 19 05:09:51 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 19 Nov 2008 03:09:51 -0700
Subject: [Cruisecontrolrb-developers] Git project building over and over
	even though there are no commits
In-Reply-To: <e3af97510811121228g420a147fq3e63c9d8e0893776@mail.gmail.com>
References: <e3af97510811121228g420a147fq3e63c9d8e0893776@mail.gmail.com>
Message-ID: <e3af97510811190209j63ef6838uf84de673b62a2abb@mail.gmail.com>

Found the root cause of this (short commit IDs are not unique, and ccrb
still doesn't detect bad return codes from source control commands):

http://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/221-git-error-short-commit-ids-are-not-always-unique

On Wed, Nov 12, 2008 at 1:28 PM, Chad Woolley <thewoolleyman at gmail.com>wrote:

> Updating to latest ccrb trunk didn't help, restarting cruise/box didn't
> work - it just builds every 5 minutes.  Working copy looks clean.
>
> Anyone seen this?
>
> This is on the new Rails CI server, if anyone wants to help debug it I can
> give access.  I don't have time right now, waiting to see if it goes away on
> the next commit.
>
> -- Chad
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081119/73e36028/attachment-0001.html>

From thewoolleyman at gmail.com  Wed Nov 26 12:46:21 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 26 Nov 2008 10:46:21 -0700
Subject: [Cruisecontrolrb-developers] CCRB tests failing
Message-ID: <e3af97510811260946k5a163025mcb8db3c387af5699@mail.gmail.com>

Hey,

The ccrb tests are failing, and I notice the CI build hasn't run since
April:

http://cruisecontrolrb.thoughtworks.com/projects

I think it is related to the SCM integration tests.  The definitely fail
when you don't have a network connection because they try to hit remote
externals, but also fail when you do have a connection.  I'll try to dig
into it, but giving a heads-up to anyone else who is ambitious.

-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081126/80dea81f/attachment.html>

From thewoolleyman at gmail.com  Fri Nov 28 13:38:18 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 28 Nov 2008 11:38:18 -0700
Subject: [Cruisecontrolrb-developers] CCRB tests failing
In-Reply-To: <e3af97510811260946k5a163025mcb8db3c387af5699@mail.gmail.com>
References: <e3af97510811260946k5a163025mcb8db3c387af5699@mail.gmail.com>
Message-ID: <e3af97510811281038u1bbe14d2x90c3d8c95ce3f5ed@mail.gmail.com>

On Wed, Nov 26, 2008 at 10:46 AM, Chad Woolley <thewoolleyman at gmail.com>wrote:

> The ccrb tests are failing, and I notice the CI build hasn't run since
> April:
>
> http://cruisecontrolrb.thoughtworks.com/projects
>
> I think it is related to the SCM integration tests.  The definitely fail
> when you don't have a network connection because they try to hit remote
> externals, but also fail when you do have a connection.  I'll try to dig
> into it, but giving a heads-up to anyone else who is ambitious.
>

Looks like Jeremy fixed the broken tests.  Couple of issues still, though:

1. CI for CCRB still not running - this is because it should point to
github.  Ticket here:
http://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/224-demo-ccrb-instance-needs-to-point-to-github-and-have-rails-removed

2. The svn external integration tests fail when running without network
connection, because they try to hit rubyforge for the external.  I have a
proposed workaround, ticket here:
http://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/223-svn-external-integration-tests-fail-when-no-network-connection

Thanks,
-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20081128/4e1fd1b1/attachment.html>