I'll take a look a bit later. It feels like the commit you mentioned is the right one, which makes me think that we can reject this ticket, but at that pace the spectest will get to turtle speeds even though all our changes will be justified.
Anyway, I'll bisect it first and then we'll have a look at what can be done to Make the Spectest Fast Again. On 2017-06-05 14:27:28, c...@zoffix.com wrote: > On Mon, 05 Jun 2017 13:28:00 -0700, elizabeth wrote: > > Generally, we don’t care about performance once we have an > > unrecoverable exception that needs to be reported. If the stresstest > > regression is caused by trying to do Levenstein on method names > > (which > > can be a lot on some objects), then maybe the performance of > > spectest/stresstest can be accounted for by *just* the tests that > > throw Method Not Found errors? > > Yeah, I think the nqp version of the exception is proof that's the > wrong commit, otherwise > it'd've got faster than even pre-commit. > > Something else was the cause, but I ran out of steam hunting it.
