Comment 2 for bug 1212768

Right now Claim.test() returns True/False. It tests memory, disk, and cpu separately and could return either a tuple of bools or a dict of True/False values with the keys indicating the resources. Then the resource tracker can update the ComputeResourcesUnavailable exception with appropriate information. It's probably best to just keep the single exception and stuff data into it because there are many possible combinations of which resources are not available.