Re: [Junit-devel] SourceForge CVS

[Curt A. <ca...@ap...>]

>>
>> I have yet to receive any kind of automated nag, only personal  
>> nags from real people.  Could something be misconfigured?  Thanks,
>>
>
I've reviewed the Gump mailing list.  There were CVS problems and  
junit build problems reported on 09-March-2006 (http:// 
marc.theaimsgroup.com/?l=gump&m=114190474119176&w=2) which went into  
the "All dressed up and no where to go" message for undeliverable  
failure messages.

The following fragments were significant for junit:


The following annotations (debug/informational/warning/error  
messages) were provided:
  -ERROR- *** Failed to update from source control. Stale contents ***



The following work was performed:
http://vmgump.apache.org/gump/public/junit/gump_work/update_junit.html
Work Name: update_junit (Type: Update)
Work ended in a state of : Failed
Elapsed:
Command Line: cvs -q -z3 -d :pserver:ano...@cv...:/ 
cvsroot/junit \
update -P -d -A  [Working Directory: /usr/local/gump/public/workspace/ 
cvs/junit]
---------------------------------------------
cvs [update aborted]: end of file from server (consult above messages  
if any)
---------------------------------------------

The previous day's message (http://marc.theaimsgroup.com/? 
l=gump&m=114181866415173&w=2) had a successful CVS checkout, but  
failed with:


versiontag:

BUILD FAILED
/x1/gump/public/workspace/junit/build.xml:21: Warning: Could not find  
file /x1/gump/public/workspace/junit/junit/runner/ 
Version.java.template to copy.


You agreed to let yourself be nagged about Gump failures on 12- 
Mar-2006 and the Gump descriptor for junit was changed by  
bil...@ap....  Though the to address is unusual, maybe it is  
acceptable.  Since the change occurred after the last reported  
failure, maybe it will work just fine when the next failure message  
comes along.  I'll raise this on ge...@gu... and take no  
action myself.