Switch mirror status delay display to average delayrelease_2010-09-22

This takes a bit more work to compute, but since we cache all of this anyway
it isn't too big of deal. Using average delay instead of last delay will be
a bit more fair on mirrors that have odd syncing schedules, as well as
exposing those that only sync once a day. Also fix an issue that will arise
with cutoff_time being calculated once, and adjust mirror score to treat
hours delay as a float rather than an integer.

Signed-off-by: Dan McGee <dan@archlinux.org>

1 files changed, 6 insertions, 3 deletions

diff --git a/templates/mirrors/status.html b/templates/mirrors/status.html
index 1e7e38a5..d89f2b41 100644
--- a/templates/mirrors/status.html
+++ b/templates/mirrors/status.html
@@ -20,8 +20,9 @@
         <tt>lastsync</tt> file on the mirror. If this file could not be
         retrieved or contained data we didn't recognize, this column will show
         'unknown'.</li>
-        <li><em>Delay:</em> The calculated mirroring delay; e.g. <code>last
-            check − last sync</code>.</li>
+        <li><em>μ Delay:</em> The calculated average mirroring delay; e.g. the
+        mean value of <code>last check − last sync</code> for each check of
+        this mirror URL.</li>
         <li><em>μ Duration:</em> The average (mean) time it took to connect and
         retrieve the <tt>lastsync</tt> file from the given URL. Note that this
         connection time is from the location of the Arch server; your geography
@@ -92,8 +93,10 @@
 <script type="text/javascript" src="/media/jquery.tablesorter.min.js"></script>
 <script type="text/javascript">
 $(document).ready(function() {
-    $("#outofsync_mirrors").add("#successful_mirrors").tablesorter(
+    $("#outofsync_mirrors").tablesorter(
         {widgets: ['zebra'], sortList: [[3,1], [5,1]]});
+    $("#successful_mirrors").tablesorter(
+        {widgets: ['zebra'], sortList: [[7,0]]});
     $("#errorlog_mirrors").tablesorter(
         {widgets: ['zebra'], sortList: [[4,1], [5,1]]});
 });