-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
llvmdev 16.0.0.rc4 #201
llvmdev 16.0.0.rc4 #201
Conversation
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 ( |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
Interesting, something is causing I remember that this happened before in clangdev, where this was caused/fixed by:
This would seem to point to the merge of conda-forge/clang-compiler-activation-feedstock#91 as the culprit, but the compilers are actually the same between
I'm not 100% if that's causing it, but what did stand out was a difference in the @isuruf, if you have an idea what's going on here, your input would be much appreciated. |
Did you run a verbose ninja build? |
So
(note I didn't shorten the lines; the |
…nda-forge-pinning 2023.03.14.16.49.28
This reverts commit a043d4a.
No description provided.