[INFO] fetching crate vk-mem-alloc 0.2.0...
[INFO] checking vk-mem-alloc-0.2.0 against try#5cafabc9f16561d7796554d5d241c3068e2bd97f for pr-135852
[INFO] extracting crate vk-mem-alloc 0.2.0 into /workspace/builds/worker-4-tc2/source
[INFO] checking vk-mem-alloc-0.2.0 against try#5cafabc9f16561d7796554d5d241c3068e2bd97f for pr-135852
[INFO] extracting crate vk-mem-alloc 0.2.0 into /workspace/builds/worker-4-tc2/source
[INFO] checking vk-mem-alloc-0.2.0 against try#5cafabc9f16561d7796554d5d241c3068e2bd97f for pr-135852
[INFO] extracting crate vk-mem-alloc 0.2.0 into /workspace/builds/worker-4-tc2/source
[INFO] checking vk-mem-alloc-0.2.0 against try#5cafabc9f16561d7796554d5d241c3068e2bd97f for pr-135852
[INFO] extracting crate vk-mem-alloc 0.2.0 into /workspace/builds/worker-4-tc2/source
[INFO] checking vk-mem-alloc-0.2.0 against try#5cafabc9f16561d7796554d5d241c3068e2bd97f for pr-135852
[INFO] extracting crate vk-mem-alloc 0.2.0 into /workspace/builds/worker-4-tc2/source


unable to download vk-mem-alloc version 0.2.0

Caused by:
    unexpected end of file