-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Build Bioconductor-BiocGenerics for linux-aarch64 #46177
Build Bioconductor-BiocGenerics for linux-aarch64 #46177
Conversation
@daler @aliciaaevans I need your help here!
https://hub.docker.com/r/involucro/tool/tags has only |
According to https://github.com/bioconda/bioconda-utils/blob/18f988d70966f6f6296170d96cc1ced51ad10392/bioconda_utils/upload.py#L80-L81 Galaxy will use a local |
It seems |
It appears that
|
The actual problem is that there is no It fails while |
It behaves the same way on
|
What is
Installing
It is the same version (0.83) but a different build. I am trying to find out where this |
I tried to reproduce the
No issues with |
Similar error ( |
I was able to reproduce it on Linux x86_64 too! But it is random - sometimes it passes, sometimes it fails with
@bgruening From other issues I see you have experience with |
I've found the issue!
On my aarch64 machine the value is
|
The problem is a bit deeper: x86_64:
aarch64:
Same issue for @daler ^^ |
89c00eb
to
0b5a72d
Compare
I tried with custom Dockerfile.mambaforge:
Both return Same for busybox.
|
For some reason |
The problem is in |
49b2706
to
59518f4
Compare
1fd53e3
to
12370fa
Compare
OK, after reading all @martin-g's notes, doing some digging, and discussing with @daler, here's what I think is going on.
@bgruening does this seem right to you? If there was an arm involucro/tool image, I think it would work around this issue for linux-arm64 the same way as linux-64. It's not ideal but that could buy some time for a longer term solution. Would getting that involve a lot of effort? (Since the latest one was from 5 years ago.) Do you have any suggestions that could fix the issue without having to do the fallback to remote execution? |
One question here:
Are those the same files ? I guess they are but I am not sure due to the missing |
I hope we fixed it with conda-forge/font-ttf-ubuntu-feedstock#3 ! |
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
This way it loads /etc/profile even for non-interactive sessions Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
... to test usage of a custom invfile.lua that uses `/bin/sh -lc ...` instead of `/bin/sh -c ...` Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
12370fa
to
9df623a
Compare
@aliciaaevans this all makes perfect sense to me. Thanks all for digging this up. I'm wondering if we can use https://quay.io/biocontainers/involucro/ (and create ARM builds), I will also try to create ARM build for the fallback container. Need time to investigate a bit. |
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
Cool! You beat me to it. 🥇 I think we probably should also still move forward with getting the fallback working for ARM in case of other packages having this issue. |
Great, thanks @bgruening! The fallback image looks to be hard-coded in involucro, but I guess that could be made configurable? |
@BiocondaBot please fetch artifacts |
Package(s) built are ready for inspection:
Docker image(s) built:
|
The recipe is |
refs: conda/conda-build#5330 bioconda/bioconda-recipes#47554 bioconda/bioconda-recipes#46177 Signed-off-by: Marcel Bargull <marcel.bargull@udo.edu>
Describe your pull request here
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add label
command.@bioconda/core
in a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify
run_exports
(see here for the rationale and comprehensive explanation).Add a
run_exports
section like this:with
...
being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}
{{ pin_subpackage("myrecipe", max_pin="x.x") }}
{{ pin_subpackage("myrecipe", max_pin="x.x") }}
(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}
(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}
while replacing
"myrecipe"
with eithername
if aname|lower
variable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update
@BiocondaBot please add label
please review & merge
label.@BiocondaBot please fetch artifacts
You can use this to test packages locally.
Note that the
@BiocondaBot please merge
command is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>
and will automatically re-post them to notify the addressed<team>
.