(note: cross posted, if you have a reason to reply, please consider your
reply-to accordingly)
TL;DR: IF you use my jenknins stats, and notice a bunch of new failures
today, they may be from commits earlier this week.
http://fucit.org/solr-jenkins-reports/
Just wanted to put out a quick note that my jenkins test failure report
system was malfunctioning from some time late monday (in the US) when my
hosting provider upgraded the OS (breaking some shared library assumptions
i didn't realize i had).
The feed scraping was still working, so when i did a quick check of the
site the "last updated" and list of recent jobs still looked correct, but
it wasn't until yesterday that i realized it wasn't extracting the test
data from each job correctly -- but it was updating the aggregate stats
file, as if there were no new failures -- so all the stats were low.
I fixed it ~18 hours ago, and they way it's setup it was able to
"backfill" *SOME* of the failed test info from the last few days (as long
as the jenkins job info hadn't been pruned by the source server) but in
general the "Past 7 days" metrics are going to be off for a few days, and
the "Past 24 hours" won't be 100% accurate for a few more hours.
Most importantly though: If you look at the reports at any point this past
week and then looked at it again atoday and think "Holy shit, something
just changed that caused a bunch of new failures!" ... that "Something"
isn't neccessarily from the past 24 hours ... it could have been much
earlier in the week, and the stats just didn't reflect it until now.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
