[RELEASE] integration v22.04 - #461
Merged
Merged
Conversation
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
[gpuCI] Forward-merge branch-22.02 to branch-22.04 [skip gpuci]
Signed-off-by: Jordan Jacobelli <jjacobelli@nvidia.com>
Remove libhwloc
Currently when I run `conda create -n test-env rapids-build-env` locally, it installs an older version of `dask` and `distributed` which is causing issues in our `devel` image builds shown in the log link below. When I create a new environment with `conda create -n test-env rapids-build-env "dask>=2022.02.1"`, it correctly installs the latest `dask` and `distributed` versions and fixes the build issue. This PR updates the `dask` and `distributed` versions to match the working version specification. - https://gpuci.gpuopenanalytics.com/job/rapidsai/job/docker/job/rapidsai-core-devel/1105/BUILD_IMAGE=rapidsai%2Frapidsai-core-dev-nightly,CUDA_VER=11.5,FROM_IMAGE=gpuci%2Frapidsai,IMAGE_TYPE=devel,LINUX_VER=ubuntu20.04,PYTHON_VER=3.8,RAPIDS_VER=22.04/console
Update `dask` & `distributed` minimum versions
This change is for cugraph gpuci testing, with scipy ver=1.6.0 and networkx ver=2.7 causing testing problems, so the solution for the time being is keeping networkx at 2.6.3 or earlier
Temp-change networkx version requirements
Add h5py dependency
This PR updates the axis files to generate `22.06` `env` packages.
This PR updates the minimum `dask`/`distributed` versions to align with rapidsai/dask-cuda#872.
Co-authored-by: GALI PREM SAGAR <sagarprem75@gmail.com>
This PR updates the `bokeh` version to align with rapidsai/cuxfilter#355.
Update `bokeh` version
Update axis for `22.06`
Update minimum `dask`/`distributed` versions
This reverts commit c3dafda. There is already a `branch-22.06` with the correct axis values for this repository. The Jenkins job for that branch was misconfigured and was building `branch-22.04` which is why the `22.06` packages never got published correctly.
Revert "Update axis for `22.06`"
Pin click version to last supported by black 22.1.0.
update panel pins, and add jinja2
This PR adds `dask`/`distributed` version specs to the `rapids-notebook-env` to ensure that the RAPIDS supported versions of these packages are installed. This should resolve an issue in our child `rapidsai/docker` images where older versions of `dask-cudf`/`cudf`/`libcudf` were being installed due to mismatched version specifications for these packages.
Add `dask`/`distributed` version specs to `rapids-notebook-env`
update datashader version
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
❄️ Code freeze for
branch-22.04and v22.04 releaseWhat does this mean?
Only critical/hotfix level issues should be merged into
branch-22.04until release (merging of this PR).What is the purpose of this PR?
branch-22.04intomainfor the release