what about moving from CIA to keenan (the bot that is sitting on #pypy-commits and did not have a single downtime since last few months) for commit messages on #pypy? CIA was down again yesterday. cheers, fijal
Hi Maciej, On Fri, Aug 29, 2008 at 12:09 +0200, Maciej Fijalkowski wrote:
I think we should give CIA some more chances to recover from the resource problem they have. it's a bit of effort to move to yet another solution (roundup detectors, changing/testing codespeak config etc.). but good to know that on #pypy-commits one can get reliable dedicated pypy commits. holger
On Fri, Aug 29, 2008 at 8:38 PM, holger krekel <holger@merlinux.eu> wrote:
Personally I think we gave it too much chances. Also I would like to rely on roundup detectors etc via CIA and only do: 1. disable commit messages from CIA 2. move keenan from #pypy-commits to #pypy that's super easy and simplifies stuff already.
Hi Maciej, On Fri, Aug 29, 2008 at 12:09 +0200, Maciej Fijalkowski wrote:
I think we should give CIA some more chances to recover from the resource problem they have. it's a bit of effort to move to yet another solution (roundup detectors, changing/testing codespeak config etc.). but good to know that on #pypy-commits one can get reliable dedicated pypy commits. holger
On Fri, Aug 29, 2008 at 8:38 PM, holger krekel <holger@merlinux.eu> wrote:
Personally I think we gave it too much chances. Also I would like to rely on roundup detectors etc via CIA and only do: 1. disable commit messages from CIA 2. move keenan from #pypy-commits to #pypy that's super easy and simplifies stuff already.
participants (2)
-
holger krekel -
Maciej Fijalkowski