Things look good to me now.
ipdb> counters_cf.get(old_vers_column, column_start='20150806',
column_reversed=True)
OrderedDict([(u'20150806', 2), (u'20150805', 2), (u'20150804', 4),
(u'20150803', 16), (u'20150802', 4), (u'20150801', 2), (u'20150731', 13),
(u'20150730', 39), (u'20150729', 50), (u
Here is the same database query from the description with information
including today.
ipdb> old_vers_column
'Ubuntu 14.04:iproute2:3.12.0-2'
ipdb> counters_cf.get(old_vers_column, column_start='20150804',
column_reversed=True, column_count=15)
OrderedDict([(u'20150804', 4), (u'20150803', 16), (u
Stefan - that sounds like a good plan to me. Looking at the crashes from
2015-08-03 we can see the following:
$ grep "^ " 20150803-iproute2-crashes.txt | awk -F, {'print $3'} | sort |
uniq -c
22 Linux 3.13.0-59-generic x86_64
1 Linux 3.13.0-61-generic x86_64
1 Linux 3.19.0-2
Maybe we should make sure that this remains a problem with the latest
kernel *-61.100. The -59 kernel caused a lot of other problems. Usually
those were related to executing a 64bit binary from a 32bit binary. But
I would not completely rule out other odd failures. So if all the
reports are with -5
** Also affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: New => Triaged
** Changed in: iproute2 (Ubuntu Trusty)
Status: New => Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => High
** Changed in: ip
