[pkg-firebird-general] Error in Fwd: [Firebird-test] Attempting to run qmtests

[Mark O'Donohue]

Hi

There is a problem in Debian/Ubuntu libeditline.so that means

/usr/bin/isql-fb < test.sql

will cut the first 64 characters for lines longer than 64 characters.

Its not Firebird problem per-se but something to be aware of until  a
new version of libeditline comes out.

Details and patch are here:
  https://bugs.launchpad.net/ubuntu/+source/editline/+bug/307652


Cheers - Mark


---------- Forwarded message ----------
From: Mark O'Donohue <mark.odonohue at gmail.com>
Date: Sat, Dec 13, 2008 at 9:38 PM
Subject: Re: [Firebird-test] Attempting to run qmtests
To: firebird-test at lists.sourceforge.net



I found the problem, and Helen will give me an i-told-you-so for it I am sure!

It seemed that any test with lines > 64 characters in length fails.

even a:

/usr/bin/isql-fb < test.sql

will ignore the first 64 characters for lines that are longer than 64
characters - this is a problem with the libeditline provided in
Unbuntu (and Debian).

Mind you it took a bit of digging though and looking at the internals
of qmtest and fbqa.py before I figured that out.

The bug doesnt occur in our older localized version of libeditline.
There isnt any reported bug for Debian or Ubuntu but someone fixed
something similar on minix-editline.  So I created a bug report for
Unbuntu.

  https://bugs.launchpad.net/ubuntu/+source/editline/+bug/307652

Then having gone that far, it wasn't too hard then to then give them a
patch to fix is as well.


Philippe Makowski wrote:
>
> Mark,
>>
>> And the actual test ran fine, when I did it by hand.
>>
> and what result if you run only one test, for example
> $qmtest run -C context.txt functional.arno.derived_tables.derived_tables_06
>

yep, I was doing that, and comparing out put to one that worked, then
I added some code within FirebirdTest to debug what was actually sent
through to isql, since it does several substitutions to the input.
Finally when dumping and comparing stdin/stderr/stdout for a working
and non-working cases, I tried the line length.

Anyway, a side effect is I've added some debugging code that will with
a switch print the SQL code, used for setup and execution when you run
the tests.

Now where was I...

Cheers - Mark