airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AIRAVATA-1724) Failed experiment due to not having a job ID get launched
Date Wed, 06 Apr 2016 17:51:25 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eroma closed AIRAVATA-1724.
---------------------------
    Resolution: Fixed

This issue is fixed. Did not see this behavior in airavata 0.16 testing.

Tested in dev.seagrid.org

> Failed experiment due to not having a job ID get launched
> ---------------------------------------------------------
>
>                 Key: AIRAVATA-1724
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1724
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: GFac
>    Affects Versions: 0.15 
>         Environment: http://dev.test-drive.airavata.org/portal/ultrascan-testing/public
>            Reporter: Eroma
>            Assignee: Shameera Rathnayaka
>
> Steps
> Experiment FAILED as explained in the parent task.
> Then the job gets QUEUED in the rescue and has the status QUEUED in PGA
> Once a job is FAILED it should not have any activities. FAILED state is end of the line.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message