openblas v0.3.27

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• [ ] Dependencies have been updated if changed: see upstream
• [ ] Tests have passed
• [ ] Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
openblas	0.3.27

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: disabled to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• scipy
• numpy

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8561499751, please use this URL for debugging.}

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[h-vetinari]

Linux-aarch64 seems to hang in test 66 (already twice, restarted a third run now), and eventually runs into the 6h timeout:

TEST 64/67 potrf:bug_695 [OK]
TEST 65/67 kernel_regress:skx_avx [OK]
##[error]The Operation will be canceled. The next steps may not contain expected logs.
##[error]The operation was canceled.
Finishing: Run docker build

CC @martin-frbg

[h-vetinari]

Third time was the charm it seems. Not sure what's happening there TBH. 🤷‍♂️

[martin-frbg]

have not had this happen and don't think there has been any recent change that could cause it, so hopefully just a rainy day in cloudland

[h-vetinari]

Looking closer, the test numbering is not constant, and the culprit is not test 66, but fork:safety (whatever number it gets); Even when it does "pass", there's a segfault somewhere

TEST 64/67 potrf:bug_695 [OK]
TEST 65/67 fork:safety [SIGNAL 11: Segmentation fault]
[OK]
TEST 66/67 kernel_regress:skx_avx [OK]
TEST 67/67 fork:safety_after_fork_in_parent [OK]

This happens not only in emulation but also on native hardware (e.g. linux-64); I don't know if fork:safety expects a segfault, but that just the name of that test has all my spidey-senses tingling, and I think it might be reasonable to disable it for conda-forge, if we cannot figure out where this is coming from...

[martin-frbg]

segfaults are certainly not expected nor encouraged in this household... but as mentioned above, I do not think any of the changes in 0.3.27 could have caused them and I did not see them in CI, local testing or the gcc compile farm