Skip to content

Make block_size of BuildHistKernel adaptive #13743

Make block_size of BuildHistKernel adaptive

Make block_size of BuildHistKernel adaptive #13743

Triggered via pull request November 13, 2025 13:04
Status Failure
Total duration 9m 30s
Artifacts

jvm_tests.yml

on: pull_request
Build libxgboost4j.so with CUDA
3m 21s
Build libxgboost4j.so with CUDA
Matrix: build-test-jvm-packages
Matrix: build-jvm-mac
Matrix: build-jvm-manylinux2014
Matrix: build-test-jvm-packages-other-os
Matrix: test-jvm-packages-gpu
Matrix: deploy-jvm-packages
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 7 warnings
Build libxgboost4j.dylib for MacOS (Intel)
Process completed with exit code 1.
Build libxgboost4j.so targeting glibc 2.17 (arch x86_64, runner linux-amd64-cpu)
Process completed with exit code 1.
Build and test JVM packages (Linux, Scala 2.12)
Process completed with exit code 1.
Build and test JVM packages (Linux, Scala 2.13)
Process completed with exit code 1.
Build libxgboost4j.so with CUDA
Process completed with exit code 1.
Build and test JVM packages (macos-15-intel)
Process completed with exit code 1.
Build libxgboost4j.dylib for MacOS (Intel)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
Build libxgboost4j.dylib for MacOS (Apple Silicon)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
Build and test JVM packages (macos-15-intel)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Build and test JVM packages (macos-15-intel)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Build and test JVM packages (windows-latest)
EnvironmentNameNotFound: Could not find conda environment: minimal You can list all discoverable environments with `conda info --envs`.
Build and test JVM packages (windows-latest)
WARNING conda.cli.main_config:_set_key(451): Key auto_activate_base is an alias of auto_activate; setting value with latter
Build and test JVM packages (windows-latest)
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.