Skip Menu |

This queue is for tickets about the Event-ExecFlow CPAN distribution.

Report information
The Basics
Id: 79002
Status: new
Priority: 0/
Queue: Event-ExecFlow

People
Owner: Nobody in particular
Requestors: dmacks [...] netspace.org
Cc:
AdminCc:

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



Subject: t/02.parallel.t "Useless use of a variable in a void context"
Date: Wed, 15 Aug 2012 20:31:05 -0400
To: bug-Event-ExecFlow [...] rt.cpan.org
From: "Daniel Macks" <dmacks [...] netspace.org>
This is one of the issues evident in Bug #55622 "Test failures (like reported by 2 smoke tests, too)", splitting it off to a separate bug because it's a simple issue that is seemingly unrelated to the actual failures. Building Event-ExecFlow-0.64 on OS X 10.6 (apple's perl-5.10.0), I get a diagnostic during self-test. In verbose-mode, the output is: t/02.parallel.t .. 1..14 ok 1 - use Event::ExecFlow; ok 2 - use Event::ExecFlow::Frontend::Term; Useless use of a variable in void context at (eval 20) line 2. ok 3 - use Event::ExecFlow::Scheduler::SimpleMax;; The line that triggers the void-context warning is line 11: use_ok('Event::ExecFlow::Scheduler::SimpleMax;'); Removing the semicolon within the quotes: use_ok('Event::ExecFlow::Scheduler::SimpleMax'); doesn't resolve the test failures, but does clear the warning. dan -- Daniel Macks dmacks@netspace.org