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
[email protected]
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.=A0 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:[email protected]]=20
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 <[email protected]>

On Jun 25, 2012, at 12:02, Patrick Amigo wrote:

> Hello,
>=20
>=20
>=20
> We are trying to  upgrade POE version 1.289 to current version POE =
1.354.
> However, we get the following error on every attempt.
>=20
>=20
>=20
> t/30_loops/io_poll/wheel_run.t ..................... 1/103
>=20
> #   Failed test 'stdio/redirection'
>=20
> #   at /usr/lib/perl5/site_perl/5.8.8/POE/Test/Loops/wheel_run.pm line
597.
>=20
> #                   'CHILD:'
>=20
> #     doesn't match '(?-xism:CHILD:PARENT:CHILD:)'
>=20
>=20
>=20
>=20
>=20
> Does anyone know a solution to this upgrade error?  Any help would be=20
> greatly appreciated.
>=20
>=20
>=20
> This is the type of server we use:
>=20
> .         CentOS 5
>=20
> .         Linux kuwait.seanalyst.com 2.6.18-53.el5 #1 SMP Mon Nov 12
> 02:22:48 EST 2007 i686 i686 i386 GNU/Linux
>=20
>=20
>=20
> Sincerely,
>=20
> Patrick
>=20
>=20
>=20