Skip to content

Merge branch 'dmlc:release_3.1.0' into release_3.1.0 #306

Merge branch 'dmlc:release_3.1.0' into release_3.1.0

Merge branch 'dmlc:release_3.1.0' into release_3.1.0 #306

Triggered via push January 14, 2026 08:34
Status Failure
Total duration 1d 0h 0m 3s
Artifacts

jvm_tests.yml

on: push
Build libxgboost4j.so with CUDA
0s
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

8 errors and 5 warnings
Build libxgboost4j.dylib for MacOS (Apple Silicon)
Process completed with exit code 1.
Build libxgboost4j.dylib for MacOS (Intel)
Process completed with exit code 1.
Build and test JVM packages (windows-latest)
Process completed with exit code 1.
Build libxgboost4j.so targeting glibc 2.17 (arch x86_64, runner linux-amd64-cpu)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build libxgboost4j.so targeting glibc 2.17 (arch aarch64, runner linux-arm64-cpu)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build and test JVM packages (Linux, Scala 2.13)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build and test JVM packages (Linux, Scala 2.12)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build libxgboost4j.so with CUDA
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build libxgboost4j.dylib for MacOS (Apple Silicon)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build libxgboost4j.dylib for MacOS (Intel)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
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)
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'.