Sometimes the natives builds of linux_aarch64 and linux_ppc64le on Travis CI don't start or fail in the queuing process, which needs restarting. This creates a bit of friction during the CTK release process
To reduce this friction, think we should switch linux_aarch64 and linux_ppc64le to "cross-compilation" on Azure. As the CTK packages are binary redists, we are not actually cross-compiling them. However the way the build architecture for Azure is setup is to use cross-compilers and different build_platform and target_platform. This would allow the builds to complete just as fast. Though it would mean that some kinds of tests (like running binaries for the target_platform) wouldn't work in cross-compilation (as they do in the native case). However this can already be an issue as we don't currently test with GPUs either
Making this change would amount to adding the following lines to the top of conda-forge.yml files for the feedstocks and re-rendering:
Sometimes the natives builds of
linux_aarch64
andlinux_ppc64le
on Travis CI don't start or fail in the queuing process, which needs restarting. This creates a bit of friction during the CTK release processTo reduce this friction, think we should switch
linux_aarch64
andlinux_ppc64le
to "cross-compilation" on Azure. As the CTK packages are binary redists, we are not actually cross-compiling them. However the way the build architecture for Azure is setup is to use cross-compilers and differentbuild_platform
andtarget_platform
. This would allow the builds to complete just as fast. Though it would mean that some kinds of tests (like running binaries for thetarget_platform
) wouldn't work in cross-compilation (as they do in the native case). However this can already be an issue as we don't currently test with GPUs eitherMaking this change would amount to adding the following lines to the top of
conda-forge.yml
files for the feedstocks and re-rendering: