You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Recent Java CI builds have been failing with a solve timeout on the conda environment. This was seen in other gpuci environments and fixed by #9951, but the Java build was not updated at that time since the changes caused CMake to fail to find the JDK native headers and libraries.
Steps/Code to reproduce bug
Run gpuci on any PR and examine the Java build logs
Expected behavior
gpuci Java build should pass
The text was updated successfully, but these errors were encountered:
I've been looking into the logs here and I think I've found something that may be contributing to this issue. After looking at the logs from this commit on Bradley's PR, it seems that mamba installed an older version of some packages.
That's likely due to thisintegration PR being merged without Jeremy's corresponding cudfPR being merged yet.
I've just merged Jeremy's cudf PR. Let's see if that resolves the cudf build issues for Java. If so, we can probably try switching the line below to use mamba install again.
Describe the bug
Recent Java CI builds have been failing with a solve timeout on the conda environment. This was seen in other gpuci environments and fixed by #9951, but the Java build was not updated at that time since the changes caused CMake to fail to find the JDK native headers and libraries.
Steps/Code to reproduce bug
Run gpuci on any PR and examine the Java build logs
Expected behavior
gpuci Java build should pass
The text was updated successfully, but these errors were encountered: