<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Add git history/log parser for tinderbox" href="https://bugs.freedesktop.org/show_bug.cgi?id=38879#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Add git history/log parser for tinderbox" href="https://bugs.freedesktop.org/show_bug.cgi?id=38879">bug 38879</a> from <a class="email" href="mailto:nthiebaud@gmail.com" title="Norbert Thiebaud <nthiebaud@gmail.com>"> Norbert Thiebaud</a> <pre>(In reply to <a href="show_bug.cgi?id=38879#c6">comment #6</a>) > > So tinderbox server could git pull every 15 minutes/whatever the minimum > display-interval is, and store the time and the corresponding git-hash of > the branches. No, that does not work. The tinderbox script save the sha of the tips and the timestamp of when they _fetched_ but you cannot rely on the timestamp of the commits themselves as they are routinely not in chronological order. the commit timestamp is dated from when you created the commit... commit appears on HEAD when they are pushed... there can be a significant amount of time between the two event... drastic differences for feature branch that get integrated Just take a look at bcc239b405478040fda46d1bf1d4f3e38506d1a3 2013-07-29 and the next commit is 41d2036bee3279928903cdada115d3e3cd022a06 2012-12-18 The tb script that spam people does not rely on dates.. but on a git log analysis between the last good commit sha and the current broken one. This of course is only relevant for 'progressive' tinderbox if/when we move to tb3, the spamming will be the job of the server since the tb client will not have a reliable 'last successful build' point</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>