App::Prove::State Problem: time

Ovid curtis_ovid_poe at yahoo.com
Sun Aug 24 12:24:31 UTC 2008


I've noticed that TAP::Parser uses the time() function to determine the (duh) time.  However, here's the relevant problem from 'perldoc -f time':

  Returns the number of non-leap seconds since whatever time the
  system considers to be the epoch, suitable for feeding to
  "gmtime" and "localtime". On most systems the epoch is 00:00:00
  UTC, January 1, 1970; a prominent exception being Mac OS Clas-
  sic which uses 00:00:00, January 1, 1904 in the current local
  time zone for its epoch.

This really isn't an issue now, but what if people want to merge results from multiple test suite states?  For example, if you have smokers on Windows, Linux, VMS, NeXT and others wanting to combine all test suite results for a module, are their epochs guaranteed to be the same?  Admittedly, we can't account for clock differences, but epoch may be problematic.

For now, I don't *think* this is a problem, but I'm not sure and I want to defer to more knowledgeable people.

Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6


More information about the tapx-dev mailing list