here is the output from running `dmake test TEST_VERBOSE=1`: 
t/mojo/daemon.t ............................
ok 1 - right status
ok 2 - right content
ok 3 - right value
ok 4 - right value
ok 5 - right value
ok 6 - right value
ok 7 - right value
ok 8 - right value
ok 9 - no reverse proxy
ok 10 - reverse proxy
ok 11 - right home directory
ok 12 - no value
ok 13 - right value
ok 14 - right value
ok 15 - no value
ok 16 - right value
ok 17 - right value
ok 18 - right reference
ok 19 - right script name
ok 20 - right reference
ok 21 - right reference
ok 22 - right error
ok 23 - right error
ok 24 - right error
ok 25 - right error
ok 26 - 'right transaction' isa 'Mojo::Transaction::HTTP'
ok 27 - right moniker
ok 28 - will be kept alive
ok 29 - right status
ok 30 - right content
ok 31 - will be kept alive
ok 32 - was kept alive
ok 33 - right status
ok 34 - right content
ok 35 - will not be kept alive
ok 36 - was kept alive
ok 37 - right status
ok 38 - right content
ok 39 - will not be kept alive
ok 40 - was not kept alive
ok 41 - right status
ok 42 - right content
ok 43 - will not be kept alive
ok 44 - right version
ok 45 - right status
ok 46 - right content
ok 47 - has connection id
ok 48 - right status
ok 49 - right content
ok 50 - transaction is finished
ok 51 - right content
ok 52 - no error
ok 53 - transaction is finished
ok 54 - right content
ok 55 - no error
ok 56 - transaction is finished
ok 57 - right content
ok 58 - no error
ok 59 - right status
ok 60 - right content
ok 61 - right status
ok 62 - right content
ok 63 - has local address
ok 64 - has local port
ok 65 - has original remote address
ok 66 - has remote address
ok 67 - has remote port
ok 68 - has local address
ok 69 - has local port
ok 70 - has remote address
ok 71 - has remote port
ok 72 - right moniker

In reply to Re^2: Mojolicious on Windows 64bit installation hangs on daemon.t by diyaz
in thread Mojolicious on Windows 64bit installation hangs on daemon.t by diyaz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.