Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Rex CPAN distribution.

Report information
The Basics
Id: 92669
Status: resolved
Priority: 0/
Queue: Rex

People
Owner: FERKI [...] cpan.org
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.44.1
Fixed in: 0.47.0



Subject: Possible precedence issue with control flow operator
The test suite is noisy in bleadperl with heaps of warnings as you can see in this sample fail report: http://www.cpantesters.org/cpan/report/39233624 Pass reports are affected as well, so I do not believe that there is a connection from the warning to the fails. But it's worth to fix before digging deeper. The reason is obvious. https://metacpan.org/source/JFRIED/Rex-0.44.1/lib/Rex/Helper/System.pm#L16 has a construct like return 1 or return 2; Which never returns 2 because of precedence. HTH && Regards, (Disclaimer: this was discovered by statistical analysis, I'm not speaking as a user)
On 2014-02-02 23:42:52, ANDK wrote: Show quoted text
> The test suite is noisy in bleadperl with heaps of warnings as you can > see in this sample fail report: > > http://www.cpantesters.org/cpan/report/39233624 > > Pass reports are affected as well, so I do not believe that there is a > connection from the warning to the fails. But it's worth to fix before > digging deeper. > > The reason is obvious. https://metacpan.org/source/JFRIED/Rex- > 0.44.1/lib/Rex/Helper/System.pm#L16 has a construct like > > return 1 or return 2; > > Which never returns 2 because of precedence. > > HTH && Regards, > > (Disclaimer: this was discovered by statistical analysis, I'm not > speaking as a user)
The issue is still there with stable perl 5.20.0 (And I am speaking as a user) Regards, Slaven
First of all, thanks for reporting this, and apologies for the extremely late answer. Second, I believe this has already been resolved in 0.47.0 (GitHub reference: https://github.com/RexOps/Rex/issues/377). cheers, FErki ps.: I'd like to suggest using our GitHub repo (https://github.com/RexOps/Rex) for reporting issues