Skip to content

[MRG] Fix appveyor error link to RuntimeWarning #165

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 16 commits into from
Oct 18, 2016
Merged

[MRG] Fix appveyor error link to RuntimeWarning #165

merged 16 commits into from
Oct 18, 2016

Conversation

glemaitre
Copy link
Member

No description provided.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-0.0003%) to 99.11% when pulling 9a9a808 on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@glemaitre glemaitre changed the title [MRG] Fix appveyor error link to RuntimeWarning [WIP] Fix appveyor error link to RuntimeWarning Oct 18, 2016
@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage remained the same at 99.11% when pulling 484af27 on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.0005%) to 99.111% when pulling e0cddbe on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.0005%) to 99.111% when pulling 39b458c on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.0008%) to 99.111% when pulling d40299c on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.001%) to 99.112% when pulling 29a959b on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-0.03%) to 99.081% when pulling cc14bea on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.002%) to 99.113% when pulling a995907 on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.002%) to 99.112% when pulling cdeaccd on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.0005%) to 99.111% when pulling d291eb0 on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-0.03%) to 99.084% when pulling 812143a on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-0.03%) to 99.085% when pulling 249c388 on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-0.03%) to 99.085% when pulling 249c388 on glemaitre:fix_appveor into 032fa7c on scikit-learn-contrib:master.

@coveralls
Copy link

coveralls commented Oct 18, 2016 •
edited
Loading

Coverage Status

Coverage increased (+0.001%) to 99.085% when pulling 8f85921 on glemaitre:fix_appveor into daba53a on scikit-learn-contrib:master.

@glemaitre
Copy link
Member Author

@chkoar @dvro I had to force the warning filter to be sure this is raising.
A package update should disable the always option.

@glemaitre glemaitre changed the title [WIP] Fix appveyor error link to RuntimeWarning [MRG] Fix appveyor error link to RuntimeWarning Oct 18, 2016
@glemaitre
Copy link
Member Author

@chkoar @dvro If you can go for merging

@glemaitre glemaitre merged commit 23c0b4c into scikit-learn-contrib:master Oct 18, 2016
christophe-rannou pushed a commit to christophe-rannou/imbalanced-learn that referenced this pull request Apr 3, 2017
@glemaitre
[MRG] Fix appveyor error link to RuntimeWarning (scikit-learn-contrib…
a4ecc12 
…#165)

* Change the unique checking

* Change type of warning

* Change runtimewarning to userwarning

* Set the warnings filters

* Add some debugging

* Downgrade python

* add some dbg

* avoid capturing the warning in logger

* Make crippy test

* Create the warning 2 subclasses

* solve an error

* check if we remove something that rise somethign before

* Try something else

* try to force the raising

* add the check estimator again

* reset appveyor
glemaitre added a commit to glemaitre/imbalanced-learn that referenced this pull request Jun 15, 2017
@glemaitre
[MRG] Fix appveyor error link to RuntimeWarning (scikit-learn-contrib…
fe864d2 
…#165)

* Change the unique checking

* Change type of warning

* Change runtimewarning to userwarning

* Set the warnings filters

* Add some debugging

* Downgrade python

* add some dbg

* avoid capturing the warning in logger

* Make crippy test

* Create the warning 2 subclasses

* solve an error

* check if we remove something that rise somethign before

* Try something else

* try to force the raising

* add the check estimator again

* reset appveyor
glemaitre added a commit to glemaitre/imbalanced-learn that referenced this pull request Jun 15, 2017
@glemaitre
[MRG] Fix appveyor error link to RuntimeWarning (scikit-learn-contrib…
0061fab 
…#165)

* Change the unique checking

* Change type of warning

* Change runtimewarning to userwarning

* Set the warnings filters

* Add some debugging

* Downgrade python

* add some dbg

* avoid capturing the warning in logger

* Make crippy test

* Create the warning 2 subclasses

* solve an error

* check if we remove something that rise somethign before

* Try something else

* try to force the raising

* add the check estimator again

* reset appveyor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@glemaitre @coveralls