-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
Updated C igraph core to 0.8.1, updated tests and updated Travis build configuration #372
Conversation
The returned eigenvalues did not match the largest magnitude eigenvalues that are returned by the R eigen function.
I believe the PR is essentially good to go, and the tests pass locally. I only encounter one issue still: after all tests succeed, I receive an error:
This seems to have to do with something with the @gaborcsardi it seems that the PR build fails because |
It seems that because of r-lib/roxygen2#822 it is necessary to first build the dll using compile_dll, otherwise the NAMESPACE file will not be correctly generated.
First compiling the DLL will require a NAMESPACE file. Generating the documentation and NAMESPACE using roxygen2 will require again *not* to have a NAMESPACE file present. Hence, it first needs to be added, and then needs to be removed again, in order to solve this catch-22.
The RNG is changed in R 3.6.0, we therefore need to explicitly use the RNG kind that was used previously, in order to pass tests.
@gaborcsardi , I updated the C core to version 0.8.1. Everything now builds correctly on R 3.5 and R 3.6. Two warnings remains:
This will be corrected in the C core version 0.8.2, but this should not pose any problems. The current development version of R shows a few issues, these mainly arise because If this PR can be merged, I can start working on adding some of the new functionality that has become available in the latest release of the C core. If there are any additional things that need to be done before this can be merged, let me know. |
@gaborcsardi Is it going to be an issue for this PR that recent R/igraph versions have not been pushed to this GitHub repo? The PR is therefore based on an older version than the current (the only version number I could see in this repo was 1.1 but the latest on CRAN is 1.2.5 ...) |
@szhorvat Latest releases are from the |
@gaborcsardi , I'm a bit lost as to the development on |
I can merge the cran branch into dev. OTOH, the C lib repo also has a cran branch that is used in the R package... |
Yes, it would be great. |
It would be nice if, since this is based on a tagged version, this meant that rigraph could be compiled against an existing igraph library (#268). |
@gaborcsardi , thanks for updating the |
We can close this in favour of PR #380. |
This PR is meant to update the R interface to the most recent
igraph
C core version.There have been a number of API changes, which also need to be reflected in the R interface.
Some issues were fixed, which affected some of the tests (actually now leading to correct results, where some tests were previously incorrect). I've also updated all statements of the form
expect_that(..., is_true())
toexpect_true(...)
(and similarly for thefalse
variant), since I got too many warnings thatis_true()
was deprecated.There are still a number of errors in the tests, which I need to check out. Incidentally, there also seems to be some bug in the
avg_nearest_neighbour_degree
when using a weighted graph, presumably there is an error there in theigraph
C core, but I have not yet managed to nail it down and make a reproducible example. For now I commented out that test in order to proceed with other tests (otherwise it aborts with afree(): invalid pointer
problem). There are also still some other errors in the tests that need to be resolved.However, I already wanted to share the progress so far, to make sure that there are no obvious things I'm overlooking or doing incorrectly. Feedback is welcome @gaborcsardi.
Note that the
functions.def
was still incorrect inigraph
. I have created PR igraph/igraph#1338 to address this, which of course affects to what commit thecigraph
submodule should point.