You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Curt Arnold <ca...@apache.org> on 2006/03/15 19:34:29 UTC
Junit nagging and CVS timeouts
Backstory: I've been on the junit mailing list for a few hours trying
to track down a problem that has recently surfaced in the log4j unit
tests on Gump that I believe is due to a change in junit. To
complicate issues, the junit anonymous CVS server has been
unresponsive, so I haven't been able to see the code in question or
reproduce it the problem locally. So I've been driving blind with a
little help from Gump.
David Saff mentioned that he had not gotten any automated failure
messages from Gump for junit, though I would have suspected some on
09-Mar-2006. So I dived into looking at the project gump descriptor,
not realizing that he had been added as the nagee on the 12-
Mar-2006. Before I realized it was a brand new entry, I did notice
that the "to" address in the junit nag contained < and > and
that no "to" address in nag elements in other projects contained
those characters. They were common in "from" addresses. Maybe it
isn't wrong, just different.
Anyway, it seemed undesirable to nag him personally instead of the
development list. Thought it may be good to use him as the sender to
get through the non-subscriber blocking and to avoid replies and
bounces to general@gump.apache.org. Any comments on changing the
junit nag as described below?
Begin forwarded message:
> From: David Saff <sa...@mit.edu>
> Date: March 15, 2006 11:55:13 AM CST
> To: Curt Arnold <ca...@apache.org>
> Cc: junit-devel@lists.sourceforge.net
> Subject: Re: [Junit-devel] SourceForge CVS
>
> Curt Arnold wrote:
>> The current project descriptor contains:
>>
>> <nag from="Gump Integration <general@gump.apache.org>"
>> to="David Saff <saff@mit.edu>" />
>>
>> I could change it to:
>>
>> <nag from="David Saff <saff@mit.edu>"
>> to="junit-devel@lists.sourceforge.net" />
>>
>> or post a request to the Gump mailing list to review your project
>> descriptor.
>
> I have no knowledge of Gump nag descriptor formatting, so I'll have
> to ask your help on this. How often are the nag messages sent? If
> it's daily or less, then sending it to junit-devel should be fine.
> Otherwise, please have it sent straight to me. Thanks,
>
> David Saff
Also, the anonymous CVS server for junit has been unresponsive as
seen in the "All dressed up" message on 09-Mar-2006 (http://
marc.theaimsgroup.com/?l=gump&m=114190474119176&w=2).
The following annotations (debug/informational/warning/error
messages) were provided:
-ERROR- *** Failed to update from source control. Stale contents ***
I thought that I saw a similar error in the log for the 14-Mar-2006
Gump run, though the 15-Mar-2006 run completed successfully. Should
a nag message had been sent if the same problem occurred yesterday?
Any documentation of CVS failures may be helpful to the SourceForge
staff in identifying the problem with the JUnit CVS or at least gives
JUnit documentation when to back up their complaints.
If source control failure does not result in a Nag message, maybe it
should be configurable to do so.
I've told David that I would raise the issues here and take no action
myself without feedback. I think it would be desirable to change the
nagee to junit-devel@lists.sourceforge.net instead of saff@mit.edu
and believe he consents since the messages should be at most daily.
I'll defer to more experienced hands on the proper from address.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Junit nagging and CVS timeouts
Posted by Steve Loughran <st...@apache.org>.
Curt Arnold wrote:
>
> On Mar 15, 2006, at 12:59 PM, Bill Barker wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: Curt Arnold [mailto:carnold@apache.org]
>>> Sent: Wednesday, March 15, 2006 10:34 AM
>>> To: Gump code and data
>>> Subject: Junit nagging and CVS timeouts
>>>
>>> Backstory: I've been on the junit mailing list for a few
>>> hours trying
>>> to track down a problem that has recently surfaced in the log4j unit
>>> tests on Gump that I believe is due to a change in junit. To
>>> complicate issues, the junit anonymous CVS server has been
>>> unresponsive, so I haven't been able to see the code in question or
>>> reproduce it the problem locally. So I've been driving blind with a
>>> little help from Gump.
>>>
>>
>> From your commit messages, I believe that it's the same Ant bug that was
>> killing commons-collections last week. The short version is that when
>> Ant
>> auto-detects JUnit-4, it doesn't look for the static suite() method, and
>> just assumes that you've defined all of your tests with Annotations.
>>
>
> Thanks, sounds like it. I'll pass it along to junit-devel. I couldn't
> find a bugzilla issue related to it and it was hard to sort through all
> the JUnit related threads on the Ant-dev mailing list.
Ant is still coming to terms with Junit4.
-There's just been a profound change in Ant's <junit> task which uses
reflection to load junit.jar, which means you dont need junit on Ant's
own classpath to use the task. We could, therefore, pull the
runtime="true" dependency on junit in ant's own descriptor, which would
break anyone who assumed that Ant came with junit.
-The junit4 support is new and stabilising; I think right now it looks
for junit3 on the classpath ahead of junit4 and goes for that first if
found, rolling back to junit4 otherwise.
-The Ant team is thinking of pulling all junit4 support out of <junit>
and into its own ant library, <junit4>, with its own test runner, XSL
transform, etc etc. <junit> is complex enough.
-Apparently the junit people want to set up a conf call with us, to
discuss <junit> futures. That call hasnt gone through yet so there is no
news. I think my #1 goal last week would have been to get them to care
about gump, but the big break is fixed there, and if the nag mail goes
to the group, they will have to care more. It may be that the remaining
change is to host the (proposed) junit4 task in the junit codebase. this
keeps the junit task+jar in perfect sync, though introduces a problem
for the junit task, namely being in sync with ant1.6 & 1.7.
-Steve
>
>
>>
>> Well, David Saff agreed to be nagged personally (check the general@gump
>> archives), not the entire junit project. There are a number of other
>> projects that nag an individual instead of the development list.
>> Since the
>> nags are usually once a day, it looks ok to change it to the junit-devel
>> list.
>>
>
> I had seen the message on general@gump, it was what alerted me to the
> recent change in the descriptor. But I saw it after I started digging
> into the apparent missed nag messages.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Junit nagging and CVS timeouts
Posted by Curt Arnold <ca...@apache.org>.
On Mar 15, 2006, at 12:59 PM, Bill Barker wrote:
>
>
>> -----Original Message-----
>> From: Curt Arnold [mailto:carnold@apache.org]
>> Sent: Wednesday, March 15, 2006 10:34 AM
>> To: Gump code and data
>> Subject: Junit nagging and CVS timeouts
>>
>> Backstory: I've been on the junit mailing list for a few
>> hours trying
>> to track down a problem that has recently surfaced in the log4j unit
>> tests on Gump that I believe is due to a change in junit. To
>> complicate issues, the junit anonymous CVS server has been
>> unresponsive, so I haven't been able to see the code in question or
>> reproduce it the problem locally. So I've been driving blind with a
>> little help from Gump.
>>
>
> From your commit messages, I believe that it's the same Ant bug
> that was
> killing commons-collections last week. The short version is that
> when Ant
> auto-detects JUnit-4, it doesn't look for the static suite()
> method, and
> just assumes that you've defined all of your tests with Annotations.
>
Thanks, sounds like it. I'll pass it along to junit-devel. I
couldn't find a bugzilla issue related to it and it was hard to sort
through all the JUnit related threads on the Ant-dev mailing list.
>
> Well, David Saff agreed to be nagged personally (check the
> general@gump
> archives), not the entire junit project. There are a number of other
> projects that nag an individual instead of the development list.
> Since the
> nags are usually once a day, it looks ok to change it to the junit-
> devel
> list.
>
I had seen the message on general@gump, it was what alerted me to the
recent change in the descriptor. But I saw it after I started
digging into the apparent missed nag messages.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: Junit nagging and CVS timeouts
Posted by Bill Barker <wb...@wilshire.com>.
> -----Original Message-----
> From: Curt Arnold [mailto:carnold@apache.org]
> Sent: Wednesday, March 15, 2006 10:34 AM
> To: Gump code and data
> Subject: Junit nagging and CVS timeouts
>
> Backstory: I've been on the junit mailing list for a few
> hours trying
> to track down a problem that has recently surfaced in the log4j unit
> tests on Gump that I believe is due to a change in junit. To
> complicate issues, the junit anonymous CVS server has been
> unresponsive, so I haven't been able to see the code in question or
> reproduce it the problem locally. So I've been driving blind with a
> little help from Gump.
>
>From your commit messages, I believe that it's the same Ant bug that was
killing commons-collections last week. The short version is that when Ant
auto-detects JUnit-4, it doesn't look for the static suite() method, and
just assumes that you've defined all of your tests with Annotations.
> David Saff mentioned that he had not gotten any automated failure
> messages from Gump for junit, though I would have suspected some on
> 09-Mar-2006. So I dived into looking at the project gump
> descriptor,
> not realizing that he had been added as the nagee on the 12-
> Mar-2006. Before I realized it was a brand new entry, I did notice
> that the "to" address in the junit nag contained < and > and
> that no "to" address in nag elements in other projects contained
> those characters. They were common in "from" addresses. Maybe it
> isn't wrong, just different.
>
> Anyway, it seemed undesirable to nag him personally instead of the
> development list. Thought it may be good to use him as the
> sender to
> get through the non-subscriber blocking and to avoid replies and
> bounces to general@gump.apache.org. Any comments on changing the
> junit nag as described below?
>
Well, David Saff agreed to be nagged personally (check the general@gump
archives), not the entire junit project. There are a number of other
projects that nag an individual instead of the development list. Since the
nags are usually once a day, it looks ok to change it to the junit-devel
list.
>
>
> Begin forwarded message:
>
> > From: David Saff <sa...@mit.edu>
> > Date: March 15, 2006 11:55:13 AM CST
> > To: Curt Arnold <ca...@apache.org>
> > Cc: junit-devel@lists.sourceforge.net
> > Subject: Re: [Junit-devel] SourceForge CVS
> >
> > Curt Arnold wrote:
> >> The current project descriptor contains:
> >>
> >> <nag from="Gump Integration <general@gump.apache.org>"
> >> to="David Saff <saff@mit.edu>" />
> >>
> >> I could change it to:
> >>
> >> <nag from="David Saff <saff@mit.edu>"
> >> to="junit-devel@lists.sourceforge.net" />
> >>
> >> or post a request to the Gump mailing list to review your project
> >> descriptor.
> >
> > I have no knowledge of Gump nag descriptor formatting, so
> I'll have
> > to ask your help on this. How often are the nag messages
> sent? If
> > it's daily or less, then sending it to junit-devel should
> be fine.
> > Otherwise, please have it sent straight to me. Thanks,
> >
> > David Saff
>
> Also, the anonymous CVS server for junit has been unresponsive as
> seen in the "All dressed up" message on 09-Mar-2006 (http://
> marc.theaimsgroup.com/?l=gump&m=114190474119176&w=2).
>
>
> The following annotations (debug/informational/warning/error
> messages) were provided:
> -ERROR- *** Failed to update from source control. Stale contents ***
>
> I thought that I saw a similar error in the log for the 14-Mar-2006
> Gump run, though the 15-Mar-2006 run completed successfully. Should
> a nag message had been sent if the same problem occurred yesterday?
> Any documentation of CVS failures may be helpful to the SourceForge
> staff in identifying the problem with the JUnit CVS or at
> least gives
> JUnit documentation when to back up their complaints.
>
> If source control failure does not result in a Nag message, maybe it
> should be configurable to do so.
>
The SF CVS repos is notorious for failing. As a result, the 'live' branch
(which is what runs on vmgump) just continues on with the stale checkout.
The clarus and helos runs are using 'trunk', which would presumably nag if
they were configured to do so.
> I've told David that I would raise the issues here and take
> no action
> myself without feedback. I think it would be desirable to
> change the
> nagee to junit-devel@lists.sourceforge.net instead of saff@mit.edu
> and believe he consents since the messages should be at most daily.
> I'll defer to more experienced hands on the proper from address.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
>
>
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org