Skip to content

[mt] Implement one-hot categorical feature for CPU hist. #14810

[mt] Implement one-hot categorical feature for CPU hist.

[mt] Implement one-hot categorical feature for CPU hist. #14810

Triggered via pull request March 11, 2026 10:24
Status Cancelled
Total duration 7m 53s
Artifacts

jvm_tests.yml

on: pull_request
Configure variables for CI
8s
Configure variables for CI
Matrix: build-jvm-mac
Matrix: build-jvm-manylinux2014
Matrix: build-test-jvm-packages-other-os
Build libxgboost4j.so with CUDA
6m 18s
Build libxgboost4j.so with CUDA
Matrix: build-test-jvm-packages-linux
Matrix: test-jvm-packages-gpu
Matrix: deploy-jvm-packages
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 6 warnings
Build libxgboost4j.dylib for MacOS (Intel)
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build libxgboost4j.dylib for MacOS (Apple Silicon)
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build and test JVM packages (macos-15-intel)
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build and test JVM packages (Linux, Scala 2.12)
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build and test JVM packages (Linux, Scala 2.12)
The operation was canceled.
Build libxgboost4j.so with CUDA
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build libxgboost4j.so with CUDA
The operation was canceled.
JVM Tests
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build and test JVM packages (windows-latest)
Canceling since a higher priority waiting request for JVM Tests-12072 exists
Build and test JVM packages (windows-latest)
The operation was canceled.
Configure variables for CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecr-login@v2.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Configure variables for CI
Your docker password is not masked. See https://github.com/aws-actions/amazon-ecr-login#docker-credentials for more information.
Build and test JVM packages (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and test JVM packages (windows-latest)
ERROR: 'conda activate "minimal"' exited with code 1.
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'.