I am reporting an unusual behavior of EnTK as I was running a workflow with a synthetic workload (sleep 5) for a new use case. The program exists fine, indicating the tasks within the pipeline within a stage(s) are DONE successfully. But the profiles show something else. EnTK tasks are done instantly without waiting for the task to finish. Below attached are the tasks sandboxes.
if __name__ == '__main__':
# Create a Pipeline object
p = Pipeline()
# Create a Stage object
s = Stage()
# Create a Task object
t = Task()
t.name = 'my.first.task' # Assign a name to the task (optional, do not use ',' or '_')
t.executable = 'sleep 5' # Assign executable to the task
# Add Task to the Stage
s.add_tasks(t)
s1 = Stage()
# Create a Task object
t1 = Task()
t1.name = 'my.sec.task' # Assign a name to the task (optional, do not use ',' or '_')
t1.executable = 'sleep 5' # Assign executable to the task
# Add Task to the Stage
s1.add_tasks(t1)
# Add Stage to the Pipeline
p.add_stages(s)
p.add_stages(s1)
# Create Appliication Manager
appman = AppManager(hostname=hostname, port=port, username=username,
password=password)
# Create a dictionary describe four mandatory keys:
# resource, walltime, and cpus
# resource is 'local.localhost' to execute locally
res_dict = {'resource' : "rutgers.amarel",
'exit_on_error' : True,
'access_schema' : "ssh",
'walltime' : 30,
'queue' : "XXXXX",
'cpus' : 16} # 1 node on Amarel with 256 GB of memory
# should be enough to run the pipeline
# Assign resource request description to the Application Manager
appman.resource_desc = res_dict
I am reporting an unusual behavior of EnTK as I was running a workflow with a synthetic workload (
sleep 5
) for a new use case. The program exists fine, indicating the tasks within the pipeline within a stage(s) areDONE
successfully. But the profiles show something else. EnTK tasks are done instantly without waiting for the task to finish. Below attached are the tasks sandboxes.task.zip