On 07/02/2008, Ron Blaschke <[EMAIL PROTECTED]> wrote: > jerry gay wrote: > > On Feb 7, 2008 5:38 AM, via RT Ted Neward > > <[EMAIL PROTECTED]> wrote: > >> > >> t/library/pg................................. > >> > >> Interestingly, a parrot.exe process is left running, even after Ctrl-C'ing > >> the console window in which the tests are running. Could very well be a > >> configuration problem, would love to know how to correct it if it is. > > > > it seems that parrot thinks you have postgres libraries installed. do > > you? you don't need them to run parrot (i don't have them installed on > > my windows system.) so, you can work around the problem by taking > > those libs out of your path, so parrot's configure won't find them. of > > course, that won't fix the problem, it just works around it. > > > > i (or someone else, please!) will have to install postgres libs in an > > environment and configure/build/test parrot to reproduce this > > behavior. this may take some time. if you intend to work with parrot > > and postgres specifically, where this integration would be important, > > let us know so we can bump up the priority. > > ~jerry > > This is with r25584, WinXP, VC9, PostgreSQL 8.3. > > Without PostgreSQL, eveythings skipped, as expected. > > $ parrot t/library/pg.t > 1..43 > ok 1 #skip skipped > ok 2 #skip skipped > ... > ok 42 #skip skipped > ok 43 #skip skipped > > > With PostgreSQL (that is, adding ...\PostgreSQL\8.3\bin to PATH): > > $ parrot t/library/pg.t > 1..43 > ok 1 - load_bytecode > ok 2 - load_bytecode Pg > ok 3 - Pg class exists > Method 'connectdb' not found for invocant of class 'Pg' > current instr.: 'main' pc 67 (t/library/pg.t:48)
Hrm, this is something I saw on FreeBSD. However, on that platform it actually fails the test rather than hanging... Paul
