summaryrefslogtreecommitdiffstats
path: root/testsuite/Testsrc/Testlib/TestClient/TestTools/TestPOSIX/TestFile.py
diff options
context:
space:
mode:
authorAlexander Sulfrian <alexander@sulfrian.net>2014-08-01 16:43:00 +0200
committerAlexander Sulfrian <alexander@sulfrian.net>2014-08-01 16:48:49 +0200
commitf0edc94f59ba82bef04d0576174035fd0f67a649 (patch)
treea1ac032ba389d1c91b7237283f88a58a34eea251 /testsuite/Testsrc/Testlib/TestClient/TestTools/TestPOSIX/TestFile.py
parentea634773e876cc054bdc4920567557462baa61a3 (diff)
downloadbcfg2-f0edc94f59ba82bef04d0576174035fd0f67a649.tar.gz
bcfg2-f0edc94f59ba82bef04d0576174035fd0f67a649.tar.bz2
bcfg2-f0edc94f59ba82bef04d0576174035fd0f67a649.zip
Reporting: do not duplicate isstale functionality
The interaction entries have a isstale() method, we do not need a template tag, that tries to figure out this on its own. The isstale() method works even better: It knows, if the interaction is the current interaction and compares the timestamp to the current time or (if it is not the current one) it compares the timestamp to the timestamp of the next interaction. So using the method of the model, you can browse the interaction history and see, if the host was stale some time in the past. Previously all interactions more than 24h ago were marked stale.
Diffstat (limited to 'testsuite/Testsrc/Testlib/TestClient/TestTools/TestPOSIX/TestFile.py')
0 files changed, 0 insertions, 0 deletions