Comment 4 for bug 1385229

Interesting. For swift archiving, there's no shell-accessible storage of any kind, which breaks some of the assumptions the current checksum calculation makes. What I'm thinking of doing is somehow multiplexing the file-like object we're reading from jenkins, and using hashlib's update method to calculate checksum of the stream as it comes in (while simultaneously feeding it to swift). We could adapt this to ssh and local storage too, so we don't even rely on the sha256sums tool to be locally installed. Maybe that'll help mitigate this a bit.