[Xapian-tickets] [Xapian] #300: Test failure : apitest, bigoaddvalue

[Xapian]

#300: Test failure : apitest, bigoaddvalue
-------------------------------+--------------------------------------------
 Reporter:  charliejuggler     |        Owner:  richard 
     Type:  defect             |       Status:  assigned
 Priority:  normal             |    Milestone:  1.0.9   
Component:  Test Suite         |      Version:  1.0.8   
 Severity:  normal             |   Resolution:          
 Keywords:                     |    Blockedby:          
 Platform:  Microsoft Windows  |     Blocking:          
-------------------------------+--------------------------------------------

Comment(by olly):

 I suggest that for now we skip instead of fail if we get both times being
 equal and exact integers.

 There is a better function to use - I noted it on IRC a while ago:

 @1214350526 <ojwb!i=olly at atreus.tartarus.org> just that windows will be
 using time() to read the current time
 @1214350533 <ojwb!i=olly at atreus.tartarus.org> so will have second
 granularity
 @1214350812 <ojwb!i=olly at atreus.tartarus.org> http://msdn.microsoft.com
 /en-us/library/ms724397(VS.85).aspx
 @1214350817 <ojwb!i=olly at atreus.tartarus.org> that seems the function to
 use
 @1214350848 <ojwb!i=olly at atreus.tartarus.org> no support for NT or the 9x
 family though
 @1214350869 <ojwb!i=olly at atreus.tartarus.org> which isn't a big deal, but
 it would be nice to at least fall back to using time()

 But as it's not available on NT or win 9x, and other platforms might be
 missing a better time function (or we may not detect it), skipping as
 described above would be good anyway.

 I'm not sure it's worthwhile adding support for above to the existing
 OmTime - we're testing
 for O() behaviour of portable code here, which I can't see varying by
 platform.  And as you say it's worth rewriting OmTime at some point.

 Hmm, in fact I think I might have a partial rewrite somewhere already - I
 certainly remember thinking about a better API myself.  It's not anywhere
 obvious on atreus or the laptop, but perhaps it's on one of the drives
 from the dead dev box.  I'll look later.

-- 
Ticket URL: <http://trac.xapian.org/ticket/300#comment:3>
Xapian <http://xapian.org/>
Xapian