RE: svn commit: rev 36821 - in gump/live
Gump is currently on 496 of 677. Finger's crossed.. Adam: The Gump runs seem to be completing now following your patches this morning. However there does seem to be a problem related to notification. The Avalon dev list is kind of flooded with repeated notification messages (mostly notifying success which is nice - but it's a flood all the same). Cheers, Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
Adam: The Gump runs seem to be completing now following your patches this morning. However there does seem to be a problem related to notification. The Avalon dev list is kind of flooded with repeated notification messages (mostly notifying success which is nice - but it's a flood all the same). I saw some, I wondered if it was my usual case of pine duplicating messages when my modem dies on me. I was fearing it might not be though... Darn, I guess I broke statistics when I (now) load them from a MySQL database, or something. Thanks for the heads-up. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 24 August 2004 21:26 To: [EMAIL PROTECTED] Subject: svn commit: rev 36821 - in gump/live: . bin cron python python/gump python/gump/admin python/gump/build python/gump/core python/gump/document/text python/gump/document/xdocs python/gump/integration python/gump/java python/gump/model python/gump/process py Adam: It seems like this commit may have broken something somewhere. The last Gump run blocked somewhere after entry 269 in the build cycle following which Gump reset itself and started a fresh run. As I'm typing we are back at 269 again and Gump has failed to generate any new info for the past 18 minutes so I figure its dead. Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
On Wed, 25 Aug 2004, Stephen McConnell wrote: It seems like this commit may have broken something somewhere. Thanks for the heads-up, I'll look. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
On Wed, 25 Aug 2004, Stephen McConnell wrote:
It seems like this commit may have broken something somewhere.
Yup, spot on. I'm finding this change (build from repository when failed in
proper build) hard to test, and (like all stuff in Python) untested lines/
characters of code are a time bomb. The 'test' workspace ought have found
this before I moved to 'public', but maybe it was just me not paying close
enough attention. I'll fix this now, and pay attention...
regards
Adam
INFO:gump: -- Perform Artifact Repository Search for : ws-jaxme
Traceback (most recent call last):
File bin/integrate.py, line 109, in ?
irun()
File bin/integrate.py, line 86, in irun
result = getRunner(run).perform()
File /usr/local/gump/public/gump/python/gump/runner/runner.py, line 208, in perform
return self.performRun()
File /usr/local/gump/public/gump/python/gump/runner/demand.py, line 199, in
performRun
self.performBuild(project)
File /usr/local/gump/public/gump/python/gump/runner/demand.py, line 129, in
performBuild
self.builder.buildProject(project)
File /usr/local/gump/public/gump/python/gump/build/builder.py, line 143, in
buildProject
self.extractFromRepository(project, languageHelper)
File /usr/local/gump/public/gump/python/gump/build/builder.py, line 439, in
extractFromRepository
log.info('Utilize %s from Gump artifact repository for id' % (path, id))
TypeError: not all arguments converted during string formatting
Process Exit Code : 1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
It seems like this commit may have broken something somewhere. Thanks for the heads-up, I'll look. Gump is currently on its third cycle - spinning on whatever is following 269. Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
Gump is currently on its third cycle - spinning on whatever is following 269. It was a project that had previously built, that failed, that Gump was attempting to locate artifacts for (in it's repository). Gump is currently on 496 of 677. Finger's crossed.. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svn commit: rev 36821 - in gump/live
-Original Message- From: Adam R. B. Jack [mailto:[EMAIL PROTECTED] Sent: 25 August 2004 06:41 To: Gump code and data Subject: RE: svn commit: rev 36821 - in gump/live Gump is currently on its third cycle - spinning on whatever is following 269. It was a project that had previously built, that failed, that Gump was attempting to locate artifacts for (in it's repository). Gump is currently on 496 of 677. Finger's crossed.. This is more exciting than CNN! Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
