Sorry for the noise - I misread the error. I missed that it was doing an
invalidation (update) in the middle of the test as well.
That failure is valid after all. Somehow the query execution count is
getting out of sync with miss/put counts. Those values should always be
equal. I'll have to tr
is the first check assertEquals( qs.getCacheHitCount(), 0 ); ?
On 7 March 2018 at 17:12, Steve Ebersole wrote:
> I am trying to finish up these caching and stats related changes, but am
> currently fighting a few remaining test failures. In my initial
> investigation IMO some of these tests are
I am trying to finish up these caching and stats related changes, but am
currently fighting a few remaining test failures. In my initial
investigation IMO some of these tests are wrong, but hoped someone(s) else
could check may expectation/belief. E.g. have a look at
`org.hibernate.test.querycach