Windows build artifacts are no longer available
roman-orekhov opened this issue · 13 comments
"The specified blob does not exist" error appears when I click on both 32bit and 64bit.
Do you care enough to recreate those?)
Ah, the issue seems to be the artifacts on AppVeyor are only preserved for 6 months. I should probably come up with a more durable solution … for the time being I've pushed some pending changes I had locally. I'm keeping the issue open until a more permanent storage solution is found.
Any updates? Worst case scenario, you could just re-run the CI pipeline.
Would like to grab the windoze binaries as well, but the artifacts expired.
Hello there,
Any news on this ? I don’t think it would be a good idea for me to compile it with wine ^^
Still the same issue, no artefacts [sic] available.
No, I haven't found a solution yet. The solution has actually gotten worse since AppVeyor has reduced the retention time to 1 month. Other platforms has similar limits too, so changing CI platform wouldn't solve the issue, just shift it around. I'm guessing that at least for tags it should be possible to create a GH release and copy the artifacts over. Anyone has any suggestions on ways to make this automatically from GH whenever I push a tag?
This might help https://www.appveyor.com/docs/deployment/github/
Dear professor, I need your clinfo artifacts urgently, I am exploring how to use opencl in cmdstanr, because cmdstanr wrote your clinfo artifacts into his official guide, without the clinfo artifacts I can't follow the guide next step , can you send me the file via email, my email is kyf990213@i.smu.edu.cn, thank you very much.
Anyone has any suggestions on ways to make this automatically from GH whenever I push a tag?
@Oblomov I recently implemented this for the OpenCL-SDK. Feel free to draw inspiration from how it's done. Currently it's Windows only, but that should cover the question here. Linux should be no different if default compiler switches are sufficient.
(Note that much of the work is creating source tarballs, because the default source artifacts GitHub creates don't have Git submodules but those are crucial for the SDK, therefore I must build them myself manually.)
@MathiasMagnus that looks like something I could take inspiration from, thank you very much, I'll try to look into this when I have some free time.
Looks like this still is an issue :( {"message":"Artifact not found or access denied."}
Looks like this still is an issue :(
{"message":"Artifact not found or access denied."}
Yep, still an issue. Any other way to verify OpenCL is working in Wine?
For those reading this, here's a fork with the build https://github.com/ahoylabs/clinfo/releases/tag/master-d2baa06
I also opened up a PR to do the same steps: #89