RFC: Jessie tests

RFC: Jessie tests

[Casey Marshall]

[-- Attachment #1: Type: text/plain, Size: 630 bytes --]

I have some tests for the new version of Jessie (our SSL provider)  
that I'm working on, but was curious if checking them in will disrupt  
anyone. Right now, the tests will only compile and run against the  
ssl-nio-branch of Classpath, and I will merge the code into the  
generics branch once it's OK to do so (that is, probably after the  
0.92 release).

So, these tests will only compile and run right now against the ssl- 
nio branch, and after the merge will work with the generics branch,  
but not with trunk. Will either situation be unreasonably disruptive?  
If not, I'll check these tests in this weekend.

Thanks.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 478 bytes --]

Re: RFC: Jessie tests

[Anthony Balkissoon]

On Wed, 2006-07-26 at 17:30 -0700, Casey Marshall wrote:
> I have some tests for the new version of Jessie (our SSL provider)  
> that I'm working on, but was curious if checking them in will disrupt  
> anyone. Right now, the tests will only compile and run against the  
> ssl-nio-branch of Classpath, and I will merge the code into the  
> generics branch once it's OK to do so (that is, probably after the  
> 0.92 release).
> 
> So, these tests will only compile and run right now against the ssl- 
> nio branch, and after the merge will work with the generics branch,  
> but not with trunk. Will either situation be unreasonably disruptive?  
> If not, I'll check these tests in this weekend.
> 
I don't think this is a problem.  They will show up as FAILs but that's
about the worst that should happen.  Doesn't bother me, but maybe
someone else has some input.

Tony

Re: RFC: Jessie tests

[Mark Wielaard]

Hi Casey,

On Thu, 2006-07-27 at 14:28 -0400, Anthony Balkissoon wrote:
> On Wed, 2006-07-26 at 17:30 -0700, Casey Marshall wrote:
> > So, these tests will only compile and run right now against the ssl- 
> > nio branch, and after the merge will work with the generics branch,  
> > but not with trunk. Will either situation be unreasonably disruptive?  
> > If not, I'll check these tests in this weekend.
> > 
> I don't think this is a problem.  They will show up as FAILs but that's
> about the worst that should happen.  Doesn't bother me, but maybe
> someone else has some input.

As Tony says, the Harness just marks those tests as FAILs for now since
they don't compile. But I think that is fine.

Cheers,

Mark