Enable warnings on travis (and make sure they are reasonable)
See original GitHub issueWe just disabled warnings on travis in #9840. I don’t think we should do that. I’ve been a bit absent lately, but I think the current state of the warnings is pretty bad. Many of these seem recent changes that require cleanup.
- catch and ignore all
ConvergenceWarning
s raised insklearn.utils.estimator_checks
done in https://github.com/scikit-learn/scikit-learn/pull/11151. - catch deprecations of min_impurity_split in tree and tree ensembles, make sure it’s not used anywhere else.
- catch deprecations of random_state in SVC tests, make sure it’s not used anywhere else.
Issue Analytics
- State:
- Created 6 years ago
- Comments:26 (26 by maintainers)
Top Results From Across the Web
Configuring Build Notifications
Travis CI can notify you about your build results through email, IRC, chat or custom webhooks. Default notification settings #.
Read more >Police personally warned Travis Scott about crowd before show
Houston's police chief visited rapper Travis Scott to express concerns about the energy level of the crowd at the Astroworld show ahead of ......
Read more >Travis Scott festival tragedy: Were warning signs missed at ...
Concerns were raised before Travis Scott's fatal festival show. Could the tragedy have been averted?
Read more >How missed warning signs at Travis Scott's Astroworld ...
A Houston Chronicle investigation uncovered critical failures by multiple authorities and missed warning signs at Travis Scott's Astroworld ...
Read more >Experts Point to Missed Warning Signs at Astroworld
From gate-crashing fans to a history of safety concerns at Travis Scott shows, red flags piled up before the Astroworld tragedy.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
if we could somehow save those warning as artifacts, then we could fail on the diff between the master’s log and the PR’s maybe?
We explicitly limit the number of iterations in common tests, which is why we get the warnings there.