[tor-commits] [stem/master] Still passing when tor's stime is zero

[atagar@xxxxxxxxxxxxxx]

commit f5971e1da626425062d8922a35b7b87447faa238
Author: Damian Johnson <atagar@xxxxxxxxxxxxxx>
Date:   Fri Apr 5 08:47:34 2013 -0700

    Still passing when tor's stime is zero
    
    The stime proc field is an integer, rounded down to the number of seconds that
    a process has been running. On my piddly little netbook tor takes long enough
    to start that this is always non-zero, but on our jenkins systems it's so quick
    that the test fails. Thanks to weasel for all of the help!
---
 test/integ/util/proc.py |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/test/integ/util/proc.py b/test/integ/util/proc.py
index 4fabfe9..24bb805 100644
--- a/test/integ/util/proc.py
+++ b/test/integ/util/proc.py
@@ -70,7 +70,7 @@ class TestProc(unittest.TestCase):
 
     self.assertEquals('tor', command)
     self.assertTrue(float(utime) > 0)
-    self.assertTrue(float(stime) > 0)
+    self.assertTrue(float(stime) >= 0)
     self.assertTrue(float(start_time) > proc.get_system_start_time())
 
   def test_get_connections(self):

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits