search

pal1000 / swiftshader-dist-win

Google SwiftShader Windows builds focused on Vulkan driver with utilities to help usage
MIT License
28 stars 5 forks source link

I can't find any artifacts to download #9

Open MohammedMehdiTBER opened 6 months ago

pal1000 commented 6 months ago

Scroll down until you find a pipeline run that took about 1hr or more to complete. Only those have artifacts. The rest of pipelines detected no code change so they stopped quickly without building swiftshader or producing artifacts.

This is the latest pipeline run with artifacts at the time of writing this: https://dev.azure.com/bontarka/swiftshader-dist-win/_build/results?buildId=3897&view=results

Also you would have known about this detail if you have red the readme more carefully:

Binaries packages are created automatically on Azure Pipelines every 8 hours if there are changes either here or with swiftshader itself. Builds will end quickly, under 10 minutes and with no binaries posted if there is no change.

BlohoJo commented 3 months ago

The Azure Pipelines don't seem to serve users and developers who want compiled binaries, as currently, all usable binaries have been deleted. The only job currently available with artifacts has failed to build properly. So, there is nothing currently available. This isn't user friendly, and is a hindrance instead of a help.

pal1000 commented 3 months ago

Try this run for now.

Also if you know how to automatically create azure release pipelines from every run pipeline with artifacts you are welcome to send a pull request.

BlohoJo commented 3 months ago

Don't know how to do that.

I usually look for build time to tell if there's artifacts or not. Even though the oldest April 5 release has artifacts, the 17 minute build time doesn't show in the runs list. It's the only release that has artifacts, and is missing LLVM. That's what I need.

Don't understand the point of deleting releases. It leaves users with nothing.

pal1000 commented 3 months ago

Don't understand the point of deleting releases. It leaves users with nothing.

It is Azure runs retention policy. It purges them automatically after a month.

It's the only release that has artifacts, and is missing LLVM. That's what I need.

Any reason why subzero build isn't an option?

BlohoJo commented 1 month ago

LLVM10 continues to fail to build. Is this going to stay like this or will it be fixed at some point? Could you please make available the last LLVM10 binary that built successfully?

tintanto commented 1 day ago

This is still an issue. This is the second day where I look for artifacts and 0 artifacts to be seen. I would recommend creating some releases on github instead. @pal1000

pal1000 commented 17 hours ago

I looked at last pipeline log with artifacts and it appears LLVM10 backend build fails due to compiler running out of heap space.

If any of you want to help you can work on converting build from Azure pipelines to GitHub actions. This is expected to touch/replace these files

Hopefully there should be no need to touch buildscript/ci/ci.cmd