it may be a harness bug, based on the github issues.