The failures make sense since the exception would not be thrown (this is the ...

The failures make sense since the exception would not be thrown (this is the changed behavior we were talking about in the parent issue, right?) And it's just that method (CsrfTokenGeneratorTest::testInvalidParameterTypes) which triggers the deprecation notice. It's not being called incorrectly from anywhere else. I think this was what was expected, correct?