Bug #82019 for REST-Neo4p: REST-Neo4p-0.2012 test time out on Windows

Sun Dec 16 06:52:59 2012 gabor [...] szabgab.com - Ticket created

Subject:	REST-Neo4p-0.2012 test time out on Windows
Date:	Sun, 16 Dec 2012 13:52:49 +0200
To:	bug-REST-Neo4p [...] rt.cpan.org
From:	Gabor Szabo <gabor [...] szabgab.com>

Strawberry Perl 5.12.3 32 bit I killed the install at that point. CPAN.pm: Building M/MA/MAJENSEN/REST-Neo4p-0.2012.tar.gz Server for live tests: [http://127.0.0.1:7474 ]http://127.0.0.1:7474 Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'REST-Neo4p' version '0.2012' (C:\strawberry\perl\bin\perl.exe Build.PL exited with 0) CPAN::Reporter: Build.PL result is 'pass', No errors. Building REST-Neo4p (C:\strawberry\perl\bin\perl.exe ./Build exited with 0) CPAN::Reporter: Build result is 'pass', No errors. MAJENSEN/REST-Neo4p-0.2012.tar.gz C:\strawberry\perl\bin\perl.exe ./Build -- OK Running Build test t\001_load.t ................ ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\002_agent.t ............... ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\003_objs.t ................ ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\004_idx.t ................. ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\005_db.t .................. ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\006_query.t ............... ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\007_accessors.t ........... ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout) t\008_batch_agent.t ......... ok # Test server unavailable : Can't connect to 127.0.0.1:7474 (timeout)

Sun Dec 16 14:40:55 2012 maj.fortinbras [...] gmail.com - Taken

Sun Dec 16 14:51:58 2012 maj.fortinbras [...] gmail.com - Correspondence added

Thanks Gabor-- This isn't a bug exactly, but I would appreciate your advice here- Most of the individual tests need an active Neo4j server to run. The build defaults to looking for an active server on localhost at port 7474 (you can set the server url and port during the Build.PL run). The tests that require an active server are skipped if one can't be found, so the tests pass nominally. The connect message is passed on so the user knows what's happening, but maybe this is misleading. Let me know what you think-- Mark

Sun Dec 16 14:51:59 2012 The RT System itself - Status changed from 'new' to 'open'

Sun Dec 16 14:58:15 2012 gabor [...] szabgab.com - Correspondence added

Subject:	Re: [rt.cpan.org #82019] REST-Neo4p-0.2012 test time out on Windows
Date:	Sun, 16 Dec 2012 21:58:05 +0200
To:	bug-REST-Neo4p [...] rt.cpan.org
From:	Gabor Szabo <gabor [...] szabgab.com>

On Sun, Dec 16, 2012 at 9:51 PM, Mark Allen Jensen via RT <bug-REST-Neo4p@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=82019 > > > Thanks Gabor-- > This isn't a bug exactly, but I would appreciate your advice here- Most > of the individual tests need an active Neo4j server to run. The build > defaults to looking for an active server on localhost at port 7474 (you > can set the server url and port during the Build.PL run). The tests that > require an active server are skipped if one can't be found, so the tests > pass nominally. The connect message is passed on so the user knows > what's happening, but maybe this is misleading. > Let me know what you think-- > Mark

I am not sure, maybe you could run these tests only when some environment variables are around (eg. NEO4J_HOST NEO4J_PORT ) and skip the tests when they are not there. Maybe if one of the test script already found out that there is no server, the others should not even look for one. Otherwise I think at least the timeout could be set shorter. Gabor ps. Probably you could get better advice on the perl-qa mailing list http://qa.perl.org/

Sat Mar 30 22:36:34 2013 maj.fortinbras [...] gmail.com - Status changed from 'open' to 'rejected'