Update Caffeine JMH benchmark once it builds again with NullAway

[msridhar]

After #1623 our Caffeine JMH benchmark fails to compile. We should get fixes into Caffeine, and then once they cut a new release, update our benchmark to use that release.

[codingkiddo]

Thanks @msridhar for opening this follow-up issue.

My understanding is that #1623 exposed valid NullAway warnings in the Caffeine JMH benchmark, so the first step is to fix the affected code upstream in Caffeine and then update NullAway’s benchmark dependency once Caffeine cuts a release.

I can take a look at the Caffeine failures and see whether there is a small upstream fix I can help with.

[msridhar]

@codingkiddo I wouldn't worry about the upstream failures. Probably they will get fixed quickly after we cut a new NullAway release. The main work here will be to update our benchmark to use the subsequent Caffeine release.

[codingkiddo]

@codingkiddo I wouldn't worry about the upstream failures. Probably they will get fixed quickly after we cut a new NullAway release. The main work here will be to update our benchmark to use the subsequent Caffeine release.

Thanks for clarifying @msridhar. That makes sense.