Vass's -r22509 change caused performance testing to fail last night because the name of the spectests execution temporary file was changed and thus was not recognized by computePerfStats.  Running computePerfStats on its own also seemed to indicate another problem, which was that it was not recognizing spectests.perfkeys, although since that line was unchanged and we have been getting results from spectests until last night, I doubt this was actually an issue.  Still, it seemed more robust to send the perfkeys file in to the call to computePerfStats.
Vass's -r22509 change caused performance testing to fail last night because the
name of the spectests execution temporary file was changed and thus was not
recognized by computePerfStats.  Running computePerfStats on its own also seemed
to indicate another problem, which was that it was not recognizing
spectests.perfkeys, although since that line was unchanged and we have been
getting results from spectests until last night, I doubt this was actually an
issue.  Still, it seemed more robust to send the perfkeys file in to the call
to computePerfStats.



git-svn-id: 88467cb1fb04b8a755be7e1ee1026be4190196ef@22515 3a8e244f-b0f2-452b-bcba-4c88e055c3ca

hildeth/chapel,CoryMcCartan/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,sungeunchoi/chapel,chizarlicious/chapel,hildeth/chapel,CoryMcCartan/chapel,CoryMcCartan/chapel,CoryMcCartan/chapel,hildeth/chapel,chizarlicious/chapel,chizarlicious/chapel,hildeth/chapel,chizarlicious/chapel,chizarlicious/chapel,sungeunchoi/chapel,sungeunchoi/chapel,CoryMcCartan/chapel,hildeth/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,hildeth/chapel,hildeth/chapel,sungeunchoi/chapel,sungeunchoi/chapel,chizarlicious/chapel,sungeunchoi/chapel,chizarlicious/chapel