[
https://issues.apache.org/jira/browse/AIRAVATA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma updated AIRAVATA-1668:
----------------------------
Description:
Two experiments launched with same application in different resources has exact
same output referring to the last resource
Steps:
1. Ran NWCHEM application in Stampede first and then on Trestles
2. After the Trestles experiment got completed both applications have the same
stdout referring to Trestles.
3. Experiment output is not correctly read
In Trestles and Stampede, in experiment folders () the correct stdout files
exists. In gw127 tmp/<experiment ID> folders also the correct stdout files
resides. Seems like the path is incorrect in the gateway.
was:
Two experiments launched with same application in different resources has exact
same output referring to the last resource
Steps:
1. Ran NWCHEM application in Stampede first and then on Trestles
2. After the Trestles experiment got completed both applications have the same
stdout referring to Trestles.
3. Experiment output is not correctly read
> Two experiments launched with same application in different resources has
> exact same output file
> ------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-1668
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1668
> Project: Airavata
> Issue Type: Bug
> Environment: http://test-drive.airavata.org/pga/public
> Reporter: Eroma
>
> Two experiments launched with same application in different resources has
> exact same output referring to the last resource
> Steps:
> 1. Ran NWCHEM application in Stampede first and then on Trestles
> 2. After the Trestles experiment got completed both applications have the
> same stdout referring to Trestles.
> 3. Experiment output is not correctly read
> In Trestles and Stampede, in experiment folders () the correct stdout files
> exists. In gw127 tmp/<experiment ID> folders also the correct stdout files
> resides. Seems like the path is incorrect in the gateway.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
