restraint-0.1.31 was just released which corrects a bug that was resulting in the flattening of the directory structure within task tarballs fetched via http. Unfortunately, the standard-test-rhts role had a bug that was masked by the bug in previous versions of restraint. As a result, all tests run using the standard-test-rhts role now fail to start due to restraint attempting to run them from the incorrect directory.

Symptoms of the problem were indicated by the following messages in each test's restraint harness.log:

** Preparing metadata
use_pty:FALSE make testinfo.desc
make: *** No rule to make target 'testinfo.desc'.  Stop.

This PR corrects the issue by appending the test subdirectory name to the task fetch URL in restraint's job.xml file as described in the restraint documentation.