-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot build avx512 binaries on Azure #50697
Comments
I see what you mean. I see from the logs that when it succeeded, it was using I can't find any way we can control which of the agents in the pool is used. If you find anything in the Azure Pipelines docs that you think would work, we can try that. We are limited to using the Microsoft-hosted agents. |
Would it be possible to detect the CPU features at runtime and enable the optimisations? |
@martin-g @aliciaaevans |
Hi,
I have written a recipe that generates binaries for different cpu instruction sets:
#50691
Sometimes, the Azure workflow is successful (https://github.com/bioconda/bioconda-recipes/runs/30100279149), sometimes it fails (https://github.com/bioconda/bioconda-recipes/pull/50691/checks?check_run_id=30107543181).
When it fails, the error log indicates that cargo was not able to build an avx512 binary (aka x86-64-v4).
From what I understand, the workflow is sometimes executed on a machine that supports avx512 instructions, and sometimes not.
How can I make sure that the Azure workflow will run successfully?
Is there any way to select a machine with a specific CPU?
The text was updated successfully, but these errors were encountered: