the jetstream benchmark is 50MB and that is a bit large to add to in-tree. lets get this on tooltool and we can use it as we do other artifacts on tooltool: https://1drv.ms/u/s!AtgqgjhJkZQqgtVd98PQIUuLgtOk0A

Tried to upload it with tooltool.py but apparently I don't have permission to upload. As far as I managed to find some info from the buildduty guys that have been before us, some bits in our LDAP my need modifications.. So others from buildduty team my have the same issue as I had today.

I would like this to have public visibility

roland is investigating with the help of the work that bogdan did earlier.

Uploaded the file and checked if the upload was done successfully.

"size": 50521343, "visibility": "public", "digest": "67702f163abcb73647ace3ad566d0e75da6d8494e9cc5cda38f6340def5922a89831b20542bd6fdffe0424de72820cd93057c6a346594e733603058b3c4e7dcc", "algorithm": "sha512", "filename": "jetstream"

there was one change I needed to make to jetstream (I had it in a followup patch in my queue), so I have a new jetstream.zip to upload: https://1drv.ms/u/s!AtgqgjhJkZQqgtVd98PQIUuLgtOk0A could you upload that and then give me the manifest information?

:jmaher, could you please update the binary file on drive?

it should be updated- just 10 lines changed in 1 file.

You updated just the zip file, and when we upload it to tooltool, we upload the binary. Please update the binary.

Uploaded the file and checked if the upload was done successfully. [ { "size": 10025531, "visibility": "public", "digest": "4ff745d55505720b4b5929476527ac0f9fd75a98151030699d3dec84cb11f24d2ab18f24c98ed063912e709c5126424fa7921080da3daaee31cf50eae5c9591a", "algorithm": "sha512", "filename": "jetstream.zip" } ]