-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
k8: add linux-aarch64 build #46559
k8: add linux-aarch64 build #46559
Conversation
e956c13
to
f95cc0b
Compare
e1bfc4a
to
256f5de
Compare
The build on Linux ARM64 has passed !
This header file should come from glibc-devel, and I think I use 2.17 now (https://github.com/bioconda/bioconda-recipes/pull/46559/files#diff-cbe8b71c6a5405b6548f57a5dff509864239159b58be047a4d535b58ea5b27eb) as the Linux ARM64 image (see #46186 (comment) for more info). |
807b3a4
to
87cd7fd
Compare
@mfansler Apologies for pinging you personally! |
@martin-g no worries about the ping! Unfortunately, nothing I immediately recognize to suggest to resolve this. I'd need to inspect some local builds to debug, and with my workload right now I likely can't dig in until next week. I'll try to swing back when I get some free time and see it isn't yet resolved. |
Magic! The build passed today on both x86_64 and aarch64 ! |
@BiocondaBot please fetch artifacts |
AzurePackage(s) built on Azure are ready for inspection:
You may also use
Docker image(s) built (images for Azure are in the LinuxArtifacts zip file above):
CircleCIPackage(s) built on CircleCI are ready for inspection:
You may also use
|
LGTM! |
@BiocondaBot please add label |
@martin-g good to hear! BTW, on Conda Forge in the near future declaring |
@@ -9,7 +9,7 @@ executors: | |||
linux-aarch64: | |||
machine: | |||
image: ubuntu-2204:current | |||
resource_class: arm.medium | |||
resource_class: arm.large |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I needed to switch to a large
VM because the build of Node.js takes more than one hour on medium
and the job is killed.
If Bioconda team thinks that it should stay medium
then I'd suggest to merge this PR with large
so that the recipe is published/released and then revert to medium
in a follow-up PR. And also add a build instructions to k8
recipe that it needs large
for a release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the meantime the Azure builds started failing:
12:47:04 �[32mBIOCONDA INFO�[0m (OUT) $BUILD_PREFIX/bin/x86_64-conda-linux-gnu-c++ -o $SRC_DIR/node-v18.19.1/out/Release/obj.target/v8_initializers/gen/torque-generated/third_party/v8/builtins/array-sort-tq-csa.o $SRC_DIR/node-v18.19.1/out/Release/obj/gen/torque-generated/third_party/v8/builtins/array-sort-tq-csa.cc '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CONF_NAME=nodejs_conf' '-DNODE_OPENSSL_HAS_QUIC' '-DICU_NO_USER_DATA_OVERRIDE' '-DV8_GYP_BUILD' '-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64' '-D__STDC_FORMAT_MACROS' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DV8_TARGET_ARCH_X64' '-DV8_HAVE_TARGET_OS' '-DV8_TARGET_OS_LINUX' '-DV8_EMBEDDER_STRING="-node.28"' '-DENABLE_DISASSEMBLER' '-DV8_PROMISE_INTERNAL_FIELD_COUNT=1' '-DV8_ENABLE_PRIVATE_MAPPING_FORK_OPTIMIZATION' '-DV8_SHORT_BUILTIN_CALLS' '-DOBJECT_PRINT' '-DV8_INTL_SUPPORT' '-DV8_ATOMIC_OBJECT_FIELD_WRITES' '-DV8_ENABLE_LAZY_SOURCE_POSITIONS' '-DV8_USE_SIPHASH' '-DV8_SHARED_RO_HEAP' '-DV8_WIN64_UNWINDING_INFO' '-DV8_ENABLE_REGEXP_INTERPRETER_THREADE...
##[warning]Free memory is lower than 5%; Currently used: 95.51%
##[warning]Free memory is lower than 5%; Currently used: 95.51%
They were passing last week but apparently the build of Node.js from sources is too heavy for the CI agents...
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
It should solve the issue with the missing <sys/auxv.h> on Linux x86_64 Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
Yey! The build is green on all platforms! Thank you, @mencian ! |
@BiocondaBot please fetch artifacts |
Package(s) built are ready for inspection:
Docker image(s) built:
|
LGTM! |
Linux x86_64 looks good too:
|
@BiocondaBot please add label |
* k8: add linux-aarch64 build Signed-off-by: Martin Tzvetanov Grigorov <[email protected]> * Try to build k8 from sources Signed-off-by: Martin Tzvetanov Grigorov <[email protected]> * Set CXXFLAGS * Add dependency to sysroot_linux-64 for a newer glibc It should solve the issue with the missing <sys/auxv.h> on Linux x86_64 Signed-off-by: Martin Tzvetanov Grigorov <[email protected]> * clean up recipe * clean up recipe * edit meta.yaml * add gcc * edit meta.yaml --------- Signed-off-by: Martin Tzvetanov Grigorov <[email protected]> Co-authored-by: Joshua Zhuang <[email protected]> Co-authored-by: mencian <[email protected]>
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>
.