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

Maintenance work #38

Merged
merged 32 commits into from
Feb 27, 2021
Merged

Maintenance work #38

merged 32 commits into from
Feb 27, 2021

Conversation

tpoisot
Copy link
Contributor

@tpoisot tpoisot commented Nov 16, 2020

This is Work in Progress to update some of the build system, documentation, etc.

Closes #37
Closes #36
Closes #35

@tpoisot
Copy link
Contributor Author

tpoisot commented Nov 16, 2020

Giving up for now.

@mkborregaard
Copy link
Member

What's the issue @tpoisot ?

@tpoisot
Copy link
Contributor Author

tpoisot commented Nov 17, 2020

What's the issue @tpoisot ?

The tests don't run because they can't load JuliaDB, even though it's in the test/Project.toml

@mschauer
Copy link
Contributor

Is this the issue?

205 WARNING: using OnlineStats.transform in module JuliaDB conflicts with an existing identifier.
206 * Testing LinkTree.jl: Error During Test at /home/runner/work/Phylo.jl/Phylo.jl/test/runtests.jl:19
207 Got exception outside of a @test
208 LoadError: ArgumentError: Package IterableTables not found in current path:
209  - Run `import Pkg; Pkg.add("IterableTables")` to install the IterableTables package.

.github/workflows/CI.yml Outdated Show resolved Hide resolved
.github/workflows/CI.yml Outdated Show resolved Hide resolved
tpoisot and others added 2 commits November 17, 2020 14:06
Co-authored-by: Moritz Schauer <moritzschauer@web.de>
Co-authored-by: Moritz Schauer <moritzschauer@web.de>
@mschauer
Copy link
Contributor

Sorry,

The princess is in another castle

  LoadError: ArgumentError: Package Random not found in current path:
250
  - Run `import Pkg; Pkg.add("Random")` to install the Random package.
251

Doesn't running Pkg.test("Phylo") locally help to check this without waiting for CI?

@mkborregaard
Copy link
Member

Is this the current state of affairs? Essentially Phylo is in an unstable state atm? Can we just get rid of JuliaDB?

@richardreeve
Copy link
Member

Let's see what @claireh93's reworking of the tests achieves. We were using JuliaDB, which is why it's tested with that. When I run the tests locally on 1.6-beta1, there are no problems.

@mkborregaard
Copy link
Member

yeah here neither I also ran the tests locally

@mkborregaard
Copy link
Member

@richardreeve @tpoisot can this be merged now? Did @claireh93 rework the tests? I'd love to use this at a workshop on Monday (in fact I'd planned to) but I'm running into issues because Phylo isn't compatible with current DataFrames

* master: (51 commits)
  Remove contains fix.
  Replace contains with occursin.
  Add fail-fast and simplify make file for docs.
  Remove branch specifier in testing.yaml
  Change back to master branch for docs build.
  Update deploydocs to new syntax.
  Default format is html and symbol no longer recognised.
  Try with 1.4
  Add Documenter.
  Add documenter.
  Test out on current branch.
  Add docs build to workflow.
  Fix bug in lcov path.
  Update lcov path.
  Can’t find lcov file.
  Add coverage processing.
  Add GH token.
  Add codecov and coveralls.
  Remove travis.
  Ape should only be installed on macos too.
  ...

# Conflicts:
#	Project.toml
@richardreeve
Copy link
Member

Working through it now. We have a bit too much going on in the github actions now, but I'll trim it down...

@coveralls
Copy link

coveralls commented Feb 27, 2021

Pull Request Test Coverage Report for Build 606553770

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 48 unchanged lines in 5 files lost coverage.
  • Overall coverage decreased (-2.5%) to 54.434%

Files with Coverage Reduction New Missed Lines %
src/Interface.jl 1 45.97%
src/LinkTree.jl 1 59.5%
src/TreeSet.jl 1 38.71%
src/trim.jl 3 90.63%
src/rcall.jl 42 0%
Totals Coverage Status
Change from base Build 520661805: -2.5%
Covered Lines: 1111
Relevant Lines: 2041

💛 - Coveralls

@richardreeve
Copy link
Member

@mkborregaard What is actually problematic about DataFrames? There's no changes to the code in this PR, but it works on my laptop without any constraints on DataFrames...

@mkborregaard
Copy link
Member

Just the bounds I think. Because compathelper isn't activated before this PR it lags behind the current version

@richardreeve richardreeve marked this pull request as ready for review February 27, 2021 17:31
@richardreeve
Copy link
Member

richardreeve commented Feb 27, 2021

Okay, @mkborregaard - all of the tests pass now, and I've added Windows here too and removed appveyor. Do you want to see whether it works for your purposes or if I've missed something and we need to add in another test? DataFrames is not used in anger in the code - it's just the default storage type for leaves for some tree types so there's no reason for it to matter. It was all just fixing things for the registrator (which may happen again I guess?).

@richardreeve richardreeve merged commit 050996a into master Feb 27, 2021
@richardreeve richardreeve deleted the update-dependencies branch February 28, 2021 00:20
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.

Use Documenter recent version DataFrames upper version Github workflows
5 participants