So this might be fixed for your purposes, but it doesn't really check the checksum yet. I'd still like to add that so I'm going to leave it open but there were some changes a while back on the testflinger-agent side, which should mean that you don't exit from testflinger poll, until that artifact is uploaded completely. Because if anything goes wrong during the artifact upload, it will fall out of that and put it into a results queue to retry. It's not until later when the results json gets uploaded that the job will be marked "complete", and at that point polling will stop listening, so by then, the artifact *must* be uploaded, which means you shouldn't get a truncated artifact unless some other network problem interferes.
So this might be fixed for your purposes, but it doesn't really check the checksum yet. I'd still like to add that so I'm going to leave it open but there were some changes a while back on the testflinger-agent side, which should mean that you don't exit from testflinger poll, until that artifact is uploaded completely. Because if anything goes wrong during the artifact upload, it will fall out of that and put it into a results queue to retry. It's not until later when the results json gets uploaded that the job will be marked "complete", and at that point polling will stop listening, so by then, the artifact *must* be uploaded, which means you shouldn't get a truncated artifact unless some other network problem interferes.