Arvados

I ran a job, it ran out of temp space (it did showed as passed and not failed which I find strange but I stopped the job's next step because I was watching it like a hawk). The job somehow when finished made my input collection (which was the output of a downloading job I had run previously) unavailable. This is very troubling since a job is corrupting input in keep and keeping the user the from accessing. The job itself was not doing anything to the data files themselves except reading them in. It ran out of memory on a final write out step and/or even in a logging step.

Ran that ran out of memory (bwamem-samtools-view step is the one that ran out of memory) :
https://workbench.su92l.arvadosapi.com/container_requests/su92l-xvhdp-mcmbdrxoouary4r

Collection that I can now not access:
su92l-4zz18-m4r33xx05xxbqti (Unavailable)

Job that originally created that collection (note it says failed just cause I messed up the cwl to pull the final results, the download worked fine I just took the data from the steps):

https://workbench.su92l.arvadosapi.com/container_requests/su92l-xvhdp-0dti96oardhk6jz

One of the original steps that created the input:
https://workbench.su92l.arvadosapi.com/container_requests/su92l-xvhdp-6y4hpvsm5muzw4f