Comment 2 for bug 1594325

I expect that this needs to be fixed for 2.0 because there is some path that would trigger it. If that's not the case, and it's only testing, then we can drop the 2.0 target.

The correct-and-trivial fix is to run it by its full path.