Actions
Story #13145
closedInclude container status & exit code in container request response
Status:
Duplicate
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Description
As a technical user of Arvados using the Python SDK or the `arv` CLI utility, I would like an easy way to find jobs which have succeeded, failed, or are still running.
Currently this involves first filtering the container_requests by and then fetching the containers for those container_requests which pass the initial filter to get additional fields which can be further checked. I would like to be able to do this in a single operation which is efficient both from a lines of code and a number of API calls point of view.
From a user point of view, the jobs/steps are either queued, running, completed successfully, failed, or canceled. I would like a simple way to filter on these states.
Updated by Tom Morris almost 7 years ago
- Related to Story #9425: [API?/Workbench] Search for a link tag value returns linked objects added
Updated by Peter Amstutz almost 7 years ago
- Is duplicate of Story #12917: Users should be able to see if a container failed from the container_request method added
Updated by Tom Morris almost 7 years ago
- Target version deleted (
Arvados Future Sprints)
Actions