Comment 10 for bug 724893

Well, it didn't jump, it started as Critical as soon as I diagnosed it.

It can very well start triggering without notice just because of some other apparently unrelated code change, not to mention hardware or workflow policy or number of packages or another debian release :)

And if it starts triggering, it will have to be bumped to critical, so better avoid the panic and fix it first.