Closed regro-cf-autotick-bot closed 3 months ago
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.
@conda-forge-admin, please rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/scikit-bio-feedstock/actions/runs/8559243062.
Yes, the build failed on linux-ppc64le at Travis. Some jobs (i.e. Python versions) passed, others - failed.
@qiyunzhu Could you close+reopen the PR to re-trigger the CI checks ?
Another option is to re-run the bot.
If it still fails then probably we can remove ppc64le
for the supported CPU architectures...
@qiyunzhu Unfortunately the ppc64le fails consistently on TravisCI. I think we have two options:
linux_ppc64le: linux_64
). See https://github.com/conda-forge/blis-feedstock/pull/29/files#diff-478786365dd93f740eb520c2faa03d7a0623273663b75472272c8ef94297bbe2 for more infoHi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
In conda-forge.yml: $.provider
=
{'linux_aarch64': 'default', 'linux_ppc64le': 'linux_64'}
.
{'linux_aarch64': 'default', 'linux_ppc64le': 'linux_64'} is not valid under any of the given schemas
Schema
{
"anyOf": [
{
"$ref": "#/$defs/provider"
},
{
"type": "null"
}
]
}
@martin-g Thanks for the advice. I am trying the 2nd option: linux_ppc64le: linux_64
. There seems to be some linting issue. Let's see if the other tests will pass.
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.
@martin-g The linux_ppc64le
build failed again (for some of the tests). It is unfortunate but let me remove ppc64le support following your 1st suggestion.
@martin-g Despite that the linux_ppc64le
line was removed from conda-forge.yml
, the ppc64le tests still started (and some of which failed). I wonder if the ppc64le recipes within the .ci_support
should also be manually removed?
Good point! I think you need to ask the conga-admin-bot to re-render Do you know how to do that? I’m on my mobile now. Sorry for not being able to give you the exact command!
On Mon, 8 Apr 2024 at 20:08, Qiyun Zhu @.***> wrote:
@martin-g https://github.com/martin-g Despite that the linux_ppc64le line was removed from conda-forge.yml, the ppc64le tests still started (and some of which failed). I wonder if the ppc64le recipes within the .ci_support should also be manually removed?
— Reply to this email directly, view it on GitHub https://github.com/conda-forge/scikit-bio-feedstock/pull/53#issuecomment-2043257725, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABYUQRNTTAIHZ5QAV6QTOTY4LFHHAVCNFSM6AAAAABFXKAEKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTGI2TONZSGU . You are receiving this because you were mentioned.Message ID: @.***>
@conda-forge-admin, please rerender
@martin-g Cool! Looks like all tests have passed. I will merge. Thank you for helping!
This feedstock is being rebuilt as part of the aarch64/ppc64le migration.
Feel free to merge the PR if CI is all green, but please don't close it without reaching out the the ARM migrators first at @conda-forge/arm-arch.
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 theconda-forge-admin
add it for you.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/8555348773, please use this URL for debugging.