Skip to Content.
Sympa Menu

freetds - RE: [freetds] Status 0.62rc4

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Status 0.62rc4
  • Date: Thu, 8 Jan 2004 11:14:39 -0500

> From: Castellano, Nicholas
> Sent: January 8, 2004 9:22 AM
> > From: Lowden, James K
> > Sent: Wednesday, January 07, 2004 4:51 PM
> >
> > I won't hold up 0.62 for the failures Bill cites. One he
> > said is "poorly designed", and the other two aren't show
> > stoppers according to Frediano, who wrote them.
>
> I know Freddy said he was going to disable the flags test.
> If the others
> aren't important they should be disabled too, otherwise bad
> PR is likely to
> result ("The FreeTDS team ships releases that don't even pass
> their own regression tests...")

Maybe. The tests pass on all other systems that I know of, and affect only
special cases of ODBC queries. I don't know if the failures owe to a poorly
designed test or if they're pointing up a real error that happens to occur
only in that one environment.

If Frediano says the tests are bogus, then, sure, let's remove them from the
release. Otherwise, I'm inclined to leave them in with a note that they'll
fail on some Solaris machines for reasons that we don't understand. If we
explain what they test, the user will be able to determine whether or not
it's relevant. If it is, perhaps another interested party will help us
triangulate what's going on.

It's not a 1.0 release. If we know a test fails on some system, it's better
to document it than remove it, unless (as you qualified) it's of no value in
the first place. It all comes down to what helps us most.

--jkl


-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page