Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Random Forest stress test failing: test_rf_host_memory_leak #3787

Open
Tracked by #4139
lowener opened this issue Apr 22, 2021 · 2 comments
Open
Tracked by #4139

[BUG] Random Forest stress test failing: test_rf_host_memory_leak #3787

lowener opened this issue Apr 22, 2021 · 2 comments
Labels
? - Needs Triage Need team to review and classify bug Something isn't working inactive-30d inactive-90d

Comments

@lowener
Copy link
Contributor

lowener commented Apr 22, 2021

Describe the bug
python/cuml/test/test_random_forest.py::test_rf_host_memory_leak[large_clf2-classification] is failing with version 0.19 with the following output:
assert (16947105792 - 16945065984) < 2000000.0

Environment details (please complete the following information):

  • Environment location: Docker
  • Linux Distro/Architecture: [Ubuntu 18.04 amd64]
  • GPU Model/Driver: [V100 and driver 460.39]
  • CUDA: [11.0]
  • Method of cuDF & cuML install: [Docker]
    • image rapidsai/rapidsai-dev-nightly:0.19-cuda11.0-devel-ubuntu18.04-py3.8
    • commit 1291502

Additional context
env.txt
test_random_forest.txt

@lowener lowener added ? - Needs Triage Need team to review and classify bug Something isn't working labels Apr 22, 2021
@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
? - Needs Triage Need team to review and classify bug Something isn't working inactive-30d inactive-90d
Projects
None yet
Development

No branches or pull requests

1 participant