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

CompatHelper: bump compat for EvoTrees to 0.16 for package test, (keep existing compat) #93

Merged

Conversation

github-actions[bot]
Copy link
Contributor

This pull request changes the compat entry for the EvoTrees package from 0.14.7, 0.15 to 0.14.7, 0.15, 0.16 for package test.
This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass before you merge this pull request.

@devmotion devmotion force-pushed the compathelper/new_version/2023-08-13-00-09-11-183-02878980728 branch from 47ba06f to 7024765 Compare August 13, 2023 00:09
@codecov
Copy link

codecov bot commented Oct 4, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (ccd72f5) 96.65% compared to head (93c770d) 96.65%.
Report is 1 commits behind head on main.

❗ Current head 93c770d differs from pull request most recent head 1a27af9. Consider uploading reports for the commit 1a27af9 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #93   +/-   ##
=======================================
  Coverage   96.65%   96.65%           
=======================================
  Files          11       11           
  Lines         867      867           
=======================================
  Hits          838      838           
  Misses         29       29           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

test/rstar.jl Outdated
@@ -25,8 +25,8 @@ end
@testset "samples input type: $wrapper" for wrapper in [Vector, Array, Tables.table]
# In practice, probably you want to use EvoTreeClassifier with early stopping
classifiers = (
EvoTreeClassifier(; nrounds=1_000, eta=0.1),
Pipeline(EvoTreeClassifier(; nrounds=1_000, eta=0.1); operation=predict_mode),
EvoTreeClassifier(; nrounds=1_000, eta=0.01),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it clear from the changelog why the parameters have to be changed? Or was the previous choice non-standard?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not from the changelog, but the failures seem to come from Evovest/EvoTrees.jl#250 changing defaults from (max_depth = 5, nbins=32) to (max_depth=6, nbins=64). Reverting either of these to the former default causes the tests to pass again.

Looks like a lot of parameter combinations cause the tests to pass, but just barely. Perhaps a better approach is to increase the rtol.

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 5, 2023

Pull Request Test Coverage Report for Build 6425341858

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 96.544%

Totals Coverage Status
Change from base Build 6418605547: 0.0%
Covered Lines: 838
Relevant Lines: 868

💛 - Coveralls

@devmotion
Copy link
Member

BTW I hope with Evovest/EvoTrees.jl#259 we will soon be able to run tests without pulling in CUDA which should fix the test issue here: https://github.com/TuringLang/MCMCDiagnosticTools.jl/actions/runs/6418332322/job/17425902139?pr=93#step:6:361

@sethaxen sethaxen closed this Oct 5, 2023
@sethaxen sethaxen reopened this Oct 5, 2023
@sethaxen sethaxen merged commit 65ca347 into main Oct 6, 2023
7 of 8 checks passed
@delete-merged-branch delete-merged-branch bot deleted the compathelper/new_version/2023-08-13-00-09-11-183-02878980728 branch October 6, 2023 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants