Previous test case only seemed to reproduce the problem due to resolver ordering.  Closes #805 for now.