Arvados

Longest running haplotypecaller: 1d21h49m:
https://workbench.su92l.arvadosapi.com/container_requests/su92l-xvhdp-iqy6soi7sz4runm (Notice that the command doesn't have the -L)

While most of the other ones are 2h to 4h range, as an example haplotypecaller_9:

https://workbench.su92l.arvadosapi.com/container_requests/su92l-xvhdp-cpoakbi81qqsbke

As we discussed before, we can't take just the name of the step to do the bookkeeping of the metrics (running time in this case, but more to come),
Currently we use: "duration:<checkpoint>#<containerUUID>" as the key where checkpoint is "haplotypecaller" and anything after "#" is ignored on summarizing results.

1. get the parent container request that has a workflow.json to compare to "the family of workflows" and use that as part of the key when storing the
2. make some kind of signature of the command used for that Container, this will take into account the command line, but also get a little more creative and have input parsing and having some extra metrics comparing input sizes for example.
3. a mix of 1 and 2, starting with one and try to get a sense of the clustering happens for all data

added branch 16462-go-sdk-patch 3e8a3101cb9191813f3c8ed557d6f189d3e42063

3e8a3101cb9191813f3c8ed557d6f189d3e42063 LGTM, thanks

9cce9619f3438011a42e5d10ca6c8584f0788381 (branch 16462-forecast-wip ) has the initial version of database tests

Note to future self/reviewer : make sure GET https://&lt;API&gt;/arvados/v1/container_requests/ works as expected

16462-forecast-wip2 (f6ccc08c3f6b1ad42f2c827b19df0300f2c3c3db) can be reviewed now, This is unfinished work but might be useful to know if I'm heading in the right direction.

I see that some of my changes broke federation:
developer-run-tests-remainder: #2227 /console

c0916b956054b2e16ff61bd33b11bfe07e81787d branch 16462-CR-datapoints

developer-run-tests: #2227