airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2622) Search airavata.log and locate job IDs returned at subsequent job ID search after submitting the job
Date Fri, 19 Jan 2018 20:12:00 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332853#comment-16332853
] 

Eroma commented on AIRAVATA-2622:
---------------------------------

This was tested using the SEAGrid js-169-144.jetstream-cloud.org jetstream slurm cluster.
The subsequent steps are functioning. In order to test this
 # We stopped job ID return at job submission
 # Then the job ID was returned in the 1st retry or the second retry of squeue command.

 

> Search airavata.log and locate job IDs returned at subsequent job ID search after submitting
the job
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2622
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2622
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata System, GFac
>    Affects Versions: 0.18
>            Reporter: Eroma
>            Assignee: Eroma
>            Priority: Major
>             Fix For: 0.18
>
>
> Currently at job submission the job ID is returned to airavata GFAC. At some job submissions
when the job ID is not returned gfac will try to retrieve it two more times. We need to confirm
that these subsequent steps are working. One way is to find and locate instances where the
job ID is returned in a subsequent step.
> This is to confirm that these steps are functioning as they are expected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message