Re: POE Upgrade error
Good morning. I could use some help with this problem. A third person reported the problem in IRC today, and six CPAN testers also reported it. I haven't been able to reproduce the problem or make much progress on it. I sent Patrick a public SSH key off-list, but I haven't heard back. My e-mail may have been caught by a filter somewhere. Here are the six failing CPAN reports. Can anyone spot a pattern in them? http://cpantesters.org/cpan/report/1f792eb6-ad79-11e1-8b69-15a10df65b4f http://cpantesters.org/cpan/report/bf31699c-ad6e-11e1-9373-e8c10df65b4f http://cpantesters.org/cpan/report/e865b668-ad6b-11e1-a563-f7010ef65b4f http://cpantesters.org/cpan/report/53a384fe-ad68-11e1-9889-91d70df65b4f http://cpantesters.org/cpan/report/1e015dcc-a303-11e1-89fa-d0960df65b4f http://cpantesters.org/cpan/report/a783e948-a173-11e1-9d6f-f6dbfa7543f5 It's not a timing problem. Tests are failing within a few seconds, not after a lengthy timeout. Ignore the elapsed times on the right... dubious results don't have them. System speeds also seem to vary, if the previous test's elapsed time is any indication. [22:07:53] t/30_loops/select/wheel_readwrite.t ok 945 ms [22:07:54] t/30_loops/select/wheel_run.t .. Dubious, test returned 1 (wstat 256, 0x100) [03:34:13] t/30_loops/io_poll/wheel_readwrite.t ... ok 1982 ms [03:34:16] t/30_loops/io_poll/wheel_run.t . Dubious, test returned 1 (wstat 256, 0x100) [04:01:41] t/30_loops/io_poll/wheel_readwrite.t ... ok 964 ms [04:01:42] t/30_loops/io_poll/wheel_run.t . Dubious, test returned 1 (wstat 256, 0x100) [04:23:11] t/30_loops/select/wheel_readwrite.t ok 1081 ms [04:23:13] t/30_loops/select/wheel_run.t .. Dubious, test returned 1 (wstat 256, 0x100) [05:37:43] t/30_loops/select/wheel_readwrite.t ok 847 ms [05:37:45] t/30_loops/select/wheel_run.t .. Dubious, test returned 1 (wstat 256, 0x100) Operating systems aren't necessarily an issue. Neither are they all using 64bit integers. Intel processors are a common thread, but they're also passing tests in droves. osname=linux, osvers=2.6.18-1.2798.fc6, archname=i686-linux-thread-multi-64int-ld osname=linux, osvers=2.6.17-1.2142_fc4, archname=i686-linux-thread-multi osname=linux, osvers=2.6.18-1.2798.fc6, archname=i686-linux-thread-multi-64int-ld osname=linux, osvers=2.6.18-1.2798.fc6, archname=i686-linux-thread-multi-64int-ld osname=linux, osvers=2.6.18-1.2798.fc6, archname=i686-linux-thread-multi-64int-ld osname=openbsd, osvers=5.1, archname=OpenBSD.i386-openbsd-64int It's affecting a wide variety of Perl versions, all of which are also passing tests in droves: Summary of my perl5 (revision 5 version 14 subversion 2) configuration Summary of my perl5 (revision 5 version 15 subversion 2) configuration Summary of my perl5 (revision 5 version 12 subversion 4) configuration Summary of my perl5 (revision 5 version 14 subversion 2) configuration Summary of my perl5 (revision 5 version 10 subversion 1) configuration Summary of my perl5 (revision 5 version 14 subversion 1) configuration Thanks! -- Rocco Caputo On Jun 26, 2012, at 12:14, Tony Wildish wrote: > Hi, > > I don't know if it helps any, but I saw this same error myself a few > days ago while installing on a system that had some baggage on it. > Clearing up (rm -rf) and installing from scratch made the problem go away. > > The 'baggage' in question comes from the fact that I don't have root > access to the system I was installing on, so I install in my own home > directory. The system has been updated a few times since, and I was > updating in case I'd fallen behind. So it could have been some > incompatibility that wasn't managed properly, or something like that. > > I'm afraid I can't give much more detail than that, I didn't really > pay much attention to it since it went away. > > Cheers, > Tony. > > On 6/25/12 7:43 PM, Patrick Amigo wrote: >> On Jun 25, 2012, at 12:02, Patrick Amigo wrote: >> >>> Hello, >>> >>> >>> >>> We are trying to upgrade POE version 1.289 to current version POE 1.354. >>> However, we get the following error on every attempt. >>> >>> >>> >>> t/30_loops/io_poll/wheel_run.t . 1/103 >>> >>> # Failed test 'stdio/redirection' >>> >>> # at /usr/lib/perl5/site_perl/5.8.8/POE/Test/Loops/wheel_run.pm line >> 597. >>> >>> # 'CHILD:' >>> >>> # doesn't match '(?-xism:CHILD:PARENT:CHILD:)'
Re: POE Upgrade error
Hi, I don't know if it helps any, but I saw this same error myself a few days ago while installing on a system that had some baggage on it. Clearing up (rm -rf) and installing from scratch made the problem go away. The 'baggage' in question comes from the fact that I don't have root access to the system I was installing on, so I install in my own home directory. The system has been updated a few times since, and I was updating in case I'd fallen behind. So it could have been some incompatibility that wasn't managed properly, or something like that. I'm afraid I can't give much more detail than that, I didn't really pay much attention to it since it went away. Cheers, Tony. On 6/25/12 7:43 PM, Patrick Amigo wrote: On Jun 25, 2012, at 12:02, Patrick Amigo wrote: Hello, We are trying to upgrade POE version 1.289 to current version POE 1.354. However, we get the following error on every attempt. t/30_loops/io_poll/wheel_run.t . 1/103 # Failed test 'stdio/redirection' # at /usr/lib/perl5/site_perl/5.8.8/POE/Test/Loops/wheel_run.pm line 597. # 'CHILD:' # doesn't match '(?-xism:CHILD:PARENT:CHILD:)'
RE: POE Upgrade error
Hello Rocco, Thank you very much for your reply. Yes, please send us a public SSH Key. By the way, the server is a VMWare virtual machine. Sincerely, Patrick Amigo pat.am...@positionresearch.com Position Research t. 760.480.8291 f. 760.480.8271 Organic Optimization Website Hosting Website Public Relations Website Design & Maintenance Website Application Development PPC Advertising CONFIDENTIALITY NOTICE: The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, please contact the sender by reply email and permanently delete the original message. -Original Message- From: Rocco Caputo [mailto:rcap...@pobox.com] Sent: Monday, June 25, 2012 9:23 AM To: POE Mailing List Subject: Re: POE Upgrade error Hi, Patrick. At first glance, the problem seems to be a buffering issue between the parent and child processes. I've never seen it before, and it seems like something that will be hard to reproduce. Did anything else change besides the version of POE? Did you upgrade the OS, Perl, and/or hardware at the same time? It could be a race condition in the test triggered by a nonstandard hardware setup. How fast is the machine? How many CPU cores does it have? Is it swapping during testing? It may be more practical for me to test POE on the machine. I can send you a public SSH key if that's feasible. -- Rocco Caputo On Jun 25, 2012, at 12:02, Patrick Amigo wrote: > Hello, > > > > We are trying to upgrade POE version 1.289 to current version POE 1.354. > However, we get the following error on every attempt. > > > > t/30_loops/io_poll/wheel_run.t . 1/103 > > # Failed test 'stdio/redirection' > > # at /usr/lib/perl5/site_perl/5.8.8/POE/Test/Loops/wheel_run.pm line 597. > > # 'CHILD:' > > # doesn't match '(?-xism:CHILD:PARENT:CHILD:)' > > > > > > Does anyone know a solution to this upgrade error? Any help would be > greatly appreciated. > > > > This is the type of server we use: > > . CentOS 5 > > . Linux kuwait.seanalyst.com 2.6.18-53.el5 #1 SMP Mon Nov 12 > 02:22:48 EST 2007 i686 i686 i386 GNU/Linux > > > > Sincerely, > > Patrick > > >
Re: POE Upgrade error
Hi, Patrick. At first glance, the problem seems to be a buffering issue between the parent and child processes. I've never seen it before, and it seems like something that will be hard to reproduce. Did anything else change besides the version of POE? Did you upgrade the OS, Perl, and/or hardware at the same time? It could be a race condition in the test triggered by a nonstandard hardware setup. How fast is the machine? How many CPU cores does it have? Is it swapping during testing? It may be more practical for me to test POE on the machine. I can send you a public SSH key if that's feasible. -- Rocco Caputo On Jun 25, 2012, at 12:02, Patrick Amigo wrote: > Hello, > > > > We are trying to upgrade POE version 1.289 to current version POE 1.354. > However, we get the following error on every attempt. > > > > t/30_loops/io_poll/wheel_run.t . 1/103 > > # Failed test 'stdio/redirection' > > # at /usr/lib/perl5/site_perl/5.8.8/POE/Test/Loops/wheel_run.pm line 597. > > # 'CHILD:' > > # doesn't match '(?-xism:CHILD:PARENT:CHILD:)' > > > > > > Does anyone know a solution to this upgrade error? Any help would be > greatly appreciated. > > > > This is the type of server we use: > > . CentOS 5 > > . Linux kuwait.seanalyst.com 2.6.18-53.el5 #1 SMP Mon Nov 12 > 02:22:48 EST 2007 i686 i686 i386 GNU/Linux > > > > Sincerely, > > Patrick > > >
