Sorry, I mixed stack traces; I just replaced the stack trace in the original message with the good one, and fixed the test in my pull request.