While investigating the biased lock revocation events (and related code) I found a small error in TestBiasedLockRevocationEvents.testBulkRevocationNoRebias() where an assertion was made against the wrong event.
Attaching a trivial patch that points to the issue.