If you're in overtime, if the cache has expired, then the test expectation must change from ->get('test') returns 1 to ->get('test') returns nothing
As I already said, this will make test to pass, but same effect will be from ok(1) because this test won't test things it's supposed to test in this case.

Failing the test because you're in overtime is a poorly written test.
Agreed, this is why I've posted this question.

But I now see the real problem, you're using EV to implement expiration, but that is something every caching module ( Cache/CHI .. ) knows how to do without an event loop; in short, the module has no use case
Modules which implement this without EV have to either lose noticeable amount of performance for cache housekeeping on each $cache->get() and $cache->set(), or require user to don't forget to manually call $cache->housekeeping() every few seconds (which usually mean adding this operation into many different places of code to guarantee it will be called often enough).

In event-based applications we can avoid both performance loss and chaos in code by simply using EV->timer to call housekeeping code internally in module. This is the use case for this module.

In reply to Re^6: How to write time-related test without race conditions? by powerman
in thread How to write time-related test without race conditions? by powerman

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.