in reply to Re^5: CPAN newbie troubles
in thread CPAN newbie troubles

And for the third time, you never call BAIL_OUT because you never reach it.

And you're wrong again. I quote again, from my previous post (emphasis mine):

PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/ar
+ch')" t/*.t
t/Term-Menu-Hierarchical.t .. 1/2 Bailout called.  Further testing stopped:  OS unsupported
Are you saying my solution doesn't work?

No. I'm saying that you are clearly unfamiliar with the situation that I asked about. Unfortunately, you also appear to be desperately struggling not to be proven wrong - and I'm really not interested in that kind of unproductive tussling.

In addition, I'm saying that my code works at least as well as yours for the purpose of working; this was never in question, it always worked. The problem is the collision with CPANtesters: I'm doing what's recommended, and not getting back the result that I'm supposed to get. You've been focusing on "fixing" my code (making it work), which it never needed - and you've never addressed the question that I asked, because you clearly don't know anything about it.

I appreciate your technical competence in other areas of Perl, and I thank you for trying with this question as well. Now please, stop trying to "fix" my code. It doesn't need it.

-- 
Education is not the filling of a pail, but the lighting of a fire.
 -- W. B. Yeats

Replies are listed 'Best First'.
Re^7: CPAN newbie troubles
by ikegami (Patriarch) on Jan 05, 2011 at 03:21 UTC

    I quote again,

    Just as irrelevant as the first time around. That's not the same output that you get from Windows.

    But you're right that I was wrong. While the first test is failing on Windows,

    # Failed test 'use Term::Menu::Hierarchical;' # at t/Term-Menu-Hierarchical.t line 9. # Tried to use 'Term::Menu::Hierarchical'. # Error: POSIX::termios not implemented on this architecture at C +:\strawberry\cpan\build\Term-Menu-Hierarchical-0.70-huc0DH\blib\lib/T +erm/Menu/Hierarchical.pm line 18. # Compilation failed in require at (eval 4) line 2. # BEGIN failed--compilation aborted at (eval 4) line 2.

    it's not preventing the BAIL_OUT from being executed. I'm so used to "BEGIN failed--compilation aborted" to being the end of the error chain. But it does continue on with

    # Failed test at t/Term-Menu-Hierarchical.t line 17. Bailout called. Further testing stopped: OS unsupported FAILED--Further testing stopped: OS unsupported dmake.EXE: Error code 255, while making 'test_dynamic'

    So BAIL_OUT is working as intended. So why are you getting FAIL reports? Well, you're not. You're getting N/A reports.

    Subject: NA Term-Menu-Hierarchical-0.70 v5.12.1 Windows (Win32)

    Full report

      So why are you getting FAIL reports? Well, you're not. You're getting N/A reports.

      Ah. That *is* useful - because I never received that particular email; the last one I got was still a FAIL rather than an NA (which is what I would have expected.) This does indeed handle my question (although now I need to go find out where that email went.) Thanks for doing the research; I hadn't realized that the info was available on the Web. That'll make troubleshooting this kind of problems a bit easier in the future.

      -- 
      Education is not the filling of a pail, but the lighting of a fire.
       -- W. B. Yeats
        Could it be that N/A reports aren't mailed? After all, you already know the OS isn't supported, so why would you want to be told?