opened
cjnolet
username_0
The increase in the number of Python warnings in our CI logs from our pytests have made it increasingly challenging to hunt through the logs searching for potential CI failures. 

In [this CI log] (https://gpuci.gpuopenanalytics.com/blue/rest/organizations/jenkins/pipelines/rapidsai/pipelines/gpuci/pipelines/cuml/pipelines/prb/pipelines/cuml-gpu-build/runs/14624/log/?start=0), almost half of the log is filled up with warnings that aren't relevant at all to the tests. We should probably ignore many of these warnings.
[BUG] Ignore excessive warnings in pytests / CI logs
issue
created
wphicks
username_1
Just to confirm, you're talking about the huge number of warnings like the following, yes?

```
  /opt/conda/envs/rapids/lib/python3.8/site-packages/sklearn/utils/validation.py:68: FutureWarning: Pass eps=0.9109496478186582 as keyword args. From version 0.25 passing these as positional arguments will result in an error
    warnings.warn("Pass {} as keyword args. From version 0.25 "
```
comment
created
JohnZed
username_2
Possible staging / elements:

- [ ] Hide scikit-learn warnings by default
- [ ] Add python wrapper that allows us to fail on any warnings (with ability for expected warnings)
- [ ] Reroute C++ logging through python logger to allow it to participate in python fail options

See also: adding log_once / warn_once to reduce spew consistently
comment
created
JohnZed
username_2
See also:
 - [ ] Adding custom SummaryWriter that will make it easier to find and view error
comment