Bug #10300
closed
Fiddlesticks at an old pipeline instance
Added by Bryan Cosca about 8 years ago.
Updated about 8 years ago.
Assigned To:
Radhika Chippada
Estimated time:
(Total: 0.00 h)
- Assigned To set to Tom Morris
- Target version set to Arvados Future Sprints
- Target version changed from Arvados Future Sprints to 2017-01-04 sprint
- Story points set to 0.5
- Status changed from New to In Progress
Display of these pipelines was failing due to runtime_constraints->min_nodes being a string for one the components and the runtime computation was expecting an integer. Converting the string to integer resolved it (in my manual testing).
For pipeline_instances/qr1hi-d1hrv-exbk1r9yrio2t1u :
"job": {
"href": "/jobs/qr1hi-8i9sb-j1r9j87apnrm6st",
. . .
"started_at": "2014-08-18T03:56:36Z",
"finished_at": "2014-08-18T04:30:57Z",
"output": "288ecf9b1a6605dd1c9fd93ed17dd762+11182",
"success": true,
"running": false,
"is_locked_by_uuid": "qr1hi-tpzed-k4ujw2npyuvffbo",
"log": "1c898474c88aca3c1baa3777dbc5e1f4+87",
"runtime_constraints": {
"docker_image": "arvados/jobs-java-bwa-samtools",
"max_tasks_per_node": "1",
"min_nodes": "2"
},
- Assigned To changed from Tom Morris to Radhika Chippada
Fixed in branch 10300-pipeline-display-error @ 9e06ce4e
- Target version changed from 2017-01-04 sprint to 2016-12-14 sprint
Ran the apps/workbench
tests locally without issues.
Is it worth to write a test case for this bug?
How about other similar cases? Is it possible that other numeric runtime constraints for old pipeline instances are saved as text?
Is it worth to write a test case for this bug?
I don't think it is needed
How about other similar cases? Is it possible that other numeric runtime constraints for old pipeline instances are saved as text?
Did a grep and found no other such runtime constraints.
Thanks.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:bdbcc4024e4320e17634fdfbdeb48a6051b0fccd.
Also available in: Atom
PDF