search: check results are non-nil before logging latency

Created by: rvantonder

It's possible rr results is nil here, and will cause a panic if we try to log. I reproduced a panic locally with a malformed query. Since writing a test for this is hard and the change is important but not invasive, let's merge this now and I'll add an e2e test after.