Wow. Even with the "fix" in, it runs correctly once, and then starts vomiting
with a similar error again as before the fix. it'll fail 20 times in a
row, then pass 20 times in a row. there's some haunted house level
shit going wrong here.
This reverts commit b121a061d8.
that unit tests use. maybe there's some magic that's supposed to
automatically use those things, even though they're hidden in deeply
buried paths with no machine predictable naming scheme. I can't
imagine that these unit tests passed before unless there is/was
some magic. I hobbled this in to working with a use lib and a
use for the module, but after doing this second one of these,
I'm having serious doubts about whether I'm just spackling over
the problem.
Scott Walters