Skip Menu |

This queue is for tickets about the Alien-XPA CPAN distribution.

Report information
The Basics
Id: 121653
Status: open
Priority: 0/
Queue: Alien-XPA

People
Owner: Nobody in particular
Requestors: CHORNY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.01
Fixed in: (no value)



Subject: alien.t hangs on Windows
# Seeded srand with seed '20170513' from local date. ok 1 - Alien::XPA responds to: cflags libs dynamic_libs bin_dir ok 2 - run xpaaccess --version # using C:\strawberry160\cpan\build\Alien-XPA-0.01-dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE ok 3 - command exited with value 0 ok 4 - run xpaaccess XPAMB:* # using C:\strawberry160\cpan\build\Alien-XPA-0.01-dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE Bail out! unable to access launched xpamb XPA$ERROR no 'xpaset' access points match template: xpamb # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 256 after test #4. XPA$WARNING: xpans needs to be running on this machine. Please start xpans using the command: /\strawberry160\cpan\build\Alien-XPA-0.01-dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin/xpans.exe -e -p 14285 -l C:\DOCUME~1\a\LOCALS~1\Temp/xpans_14285.log Once xpans is running, register all xpas in this process using: xpaset -p a00020f:1067 -nsconnect For now, contact xpamb using: xpaset a00020f:1067 .. or xpaget a00020f:1067 .. (hangs) After I run the test, xpamb is present in task list, probably that's why program can't exit. -- Alexandr Ciornii, http://chorny.net
On Sat May 13 09:07:37 2017, CHORNY wrote: Show quoted text
> # Seeded srand with seed '20170513' from local date. > ok 1 - Alien::XPA responds to: cflags libs dynamic_libs bin_dir > ok 2 - run xpaaccess --version > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > ok 3 - command exited with value 0 > ok 4 - run xpaaccess XPAMB:* > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > Bail out! unable to access launched xpamb > XPA$ERROR no 'xpaset' access points match template: xpamb > # Tests were run but no plan was declared and done_testing() was not > seen. > # Looks like your test exited with 256 after test #4. > XPA$WARNING: xpans needs to be running on this machine. > Please start xpans using the command: > /\strawberry160\cpan\build\Alien-XPA-0.01- > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin/xpans.exe -e -p 14285 -l > C:\DOCUME~1\a\LOCALS~1\Temp/xpans_14285.log > Once xpans is running, register all xpas in this process using: > xpaset -p a00020f:1067 -nsconnect > For now, contact xpamb using: xpaset a00020f:1067 .. or xpaget > a00020f:1067 .. > (hangs) > > > After I run the test, xpamb is present in task list, probably that's > why program can't exit.
On Sat May 13 09:07:37 2017, CHORNY wrote: Show quoted text
> # Seeded srand with seed '20170513' from local date. > ok 1 - Alien::XPA responds to: cflags libs dynamic_libs bin_dir > ok 2 - run xpaaccess --version > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > ok 3 - command exited with value 0 > ok 4 - run xpaaccess XPAMB:* > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > Bail out! unable to access launched xpamb > XPA$ERROR no 'xpaset' access points match template: xpamb > # Tests were run but no plan was declared and done_testing() was not > seen. > # Looks like your test exited with 256 after test #4. > XPA$WARNING: xpans needs to be running on this machine. > Please start xpans using the command: > /\strawberry160\cpan\build\Alien-XPA-0.01- > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin/xpans.exe -e -p 14285 -l > C:\DOCUME~1\a\LOCALS~1\Temp/xpans_14285.log > Once xpans is running, register all xpas in this process using: > xpaset -p a00020f:1067 -nsconnect > For now, contact xpamb using: xpaset a00020f:1067 .. or xpaget > a00020f:1067 .. > (hangs) > > > After I run the test, xpamb is present in task list, probably that's > why program can't exit.
I'm not sure what's going wrong here. The way XPA is supposed to work is that whenever an XPA server starts (in this case xpamb) it starts up a name server (the xpans process) and XPA clients talk to it to find the servers. The error message indicates that the xpans process is not being started up, which is why the tests fail, and which is why the -exit command is never being sent to xpamb, which is what should cause xpamb to exit. I'll have to get access to a Windows box to further diagnose this...
On Mon May 15 13:44:14 2017, DJERIUS wrote: Show quoted text
> On Sat May 13 09:07:37 2017, CHORNY wrote:
> > # Seeded srand with seed '20170513' from local date. > > ok 1 - Alien::XPA responds to: cflags libs dynamic_libs bin_dir > > ok 2 - run xpaaccess --version > > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > > ok 3 - command exited with value 0 > > ok 4 - run xpaaccess XPAMB:* > > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > > Bail out! unable to access launched xpamb > > XPA$ERROR no 'xpaset' access points match template: xpamb > > # Tests were run but no plan was declared and done_testing() was not > > seen. > > # Looks like your test exited with 256 after test #4. > > XPA$WARNING: xpans needs to be running on this machine. > > Please start xpans using the command: > > /\strawberry160\cpan\build\Alien-XPA-0.01- > > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin/xpans.exe -e -p 14285 > > -l > > C:\DOCUME~1\a\LOCALS~1\Temp/xpans_14285.log > > Once xpans is running, register all xpas in this process using: > > xpaset -p a00020f:1067 -nsconnect > > For now, contact xpamb using: xpaset a00020f:1067 .. or xpaget > > a00020f:1067 .. > > (hangs) > > > > > > After I run the test, xpamb is present in task list, probably that's > > why program can't exit.
> > I'm not sure what's going wrong here. The way XPA is supposed to work > is that whenever an XPA server starts (in this case xpamb) it starts > up a name server (the xpans process) and XPA clients talk to it to > find the servers. The error message indicates that the xpans process > is not being started up, which is why the tests fail, and which is why > the -exit command is never being sent to xpamb, which is what should > cause xpamb to exit. > > I'll have to get access to a Windows box to further diagnose this...
I've incorporated your changes from https://github.com/djerius/Alien-XPA/pull/1 and made a couple of other fixes. version 0.02-TRIAL has been pushed to CPAN. We'll see how that fares. Thanks!
On Tue May 16 16:18:02 2017, DJERIUS wrote: Show quoted text
> On Mon May 15 13:44:14 2017, DJERIUS wrote:
> > On Sat May 13 09:07:37 2017, CHORNY wrote:
> > > # Seeded srand with seed '20170513' from local date. > > > ok 1 - Alien::XPA responds to: cflags libs dynamic_libs bin_dir > > > ok 2 - run xpaaccess --version > > > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > > > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > > > ok 3 - command exited with value 0 > > > ok 4 - run xpaaccess XPAMB:* > > > # using C:\strawberry160\cpan\build\Alien-XPA-0.01- > > > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin\xpaaccess.EXE > > > Bail out! unable to access launched xpamb > > > XPA$ERROR no 'xpaset' access points match template: xpamb > > > # Tests were run but no plan was declared and done_testing() was > > > not > > > seen. > > > # Looks like your test exited with 256 after test #4. > > > XPA$WARNING: xpans needs to be running on this machine. > > > Please start xpans using the command: > > > /\strawberry160\cpan\build\Alien-XPA-0.01- > > > dpH4nN\blib\lib\auto\share\dist\Alien-XPA\bin/xpans.exe -e -p 14285 > > > -l > > > C:\DOCUME~1\a\LOCALS~1\Temp/xpans_14285.log > > > Once xpans is running, register all xpas in this process using: > > > xpaset -p a00020f:1067 -nsconnect > > > For now, contact xpamb using: xpaset a00020f:1067 .. or xpaget > > > a00020f:1067 .. > > > (hangs) > > > > > > > > > After I run the test, xpamb is present in task list, probably > > > that's > > > why program can't exit.
> > > > I'm not sure what's going wrong here. The way XPA is supposed to > > work > > is that whenever an XPA server starts (in this case xpamb) it starts > > up a name server (the xpans process) and XPA clients talk to it to > > find the servers. The error message indicates that the xpans process > > is not being started up, which is why the tests fail, and which is > > why > > the -exit command is never being sent to xpamb, which is what should > > cause xpamb to exit. > > > > I'll have to get access to a Windows box to further diagnose this...
> > I've incorporated your changes from https://github.com/djerius/Alien- > XPA/pull/1 and made a couple of other fixes. > > version 0.02-TRIAL has been pushed to CPAN. We'll see how that fares. > > Thanks!
It does not seem to have fared well at all on your smokers. Would you please be so kind as to take a look at them and let me know what happened? Thanks, Diab
On Wed May 17 16:31:48 2017, DJERIUS wrote: Show quoted text
> It does not seem to have fared well at all on your smokers. Would you > please be so kind as to take a look at them and let me know what > happened?
There are several errors: 1. Undefined subroutine &main::test_requires called at Makefile.PL line 85. 2. Win32::Process::NORMAL_PRIORITY_CLASS+Win32::Process::CREATE_NO_WINDOW should be Win32::Process::NORMAL_PRIORITY_CLASS|Win32::Process::CREATE_NO_WINDOW | instead of +, otherwise it is interpreted as Win32::Process::NORMAL_PRIORITY_CLASS(Win32::Process::CREATE_NO_WINDOW()). 3. It still reports "Bail out! unable to access launched xpamb". But does not hang. -- Alexandr Ciornii, http://chorny.net
On Thu May 18 05:30:23 2017, CHORNY wrote: Show quoted text
> On Wed May 17 16:31:48 2017, DJERIUS wrote: >
> > It does not seem to have fared well at all on your smokers. Would > > you > > please be so kind as to take a look at them and let me know what > > happened?
> > There are several errors: > 1. > Undefined subroutine &main::test_requires called at Makefile.PL line > 85. > > 2. > Win32::Process::NORMAL_PRIORITY_CLASS+Win32::Process::CREATE_NO_WINDOW > should be > Win32::Process::NORMAL_PRIORITY_CLASS|Win32::Process::CREATE_NO_WINDOW > > | instead of +, otherwise it is interpreted as > Win32::Process::NORMAL_PRIORITY_CLASS(Win32::Process::CREATE_NO_WINDOW()). > > 3. > It still reports "Bail out! unable to access launched xpamb". But > does not hang.
Thanks. I prematurely uploaded a release which fixes (1) before I saw this reply. I'll fix (2) and upload a new release. As for (3)? I'm not sure how to proceed. At least it doesn't hang any more!