-
-
Notifications
You must be signed in to change notification settings - Fork 206
fix: Fix tests on next branch #2058
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
base: next
Are you sure you want to change the base?
Conversation
Can you elaborate on " games sometimes hangs on my system"? Most of these seem straighforward issues related to changes in functions arguments. Some functions gained new arguments, some had arguments removed. For example, The reasons for each change should be clear from https://github.com/igraph/igraph/blob/develop/CHANGELOG.md — if not, we need to improve the changelog. |
AI-generated summary of the test output: Here’s a structured summary of the error patterns you encountered, ordered by frequency: ⸻
⸻
⸻
⸻
⸻
⸻
⸻
⸻
⸻ Summary by Category ⸻ 👉 Would you like me to tabulate these error categories with counts per test file so you can immediately see which files contribute most to failures? |
|
For the top of the list,
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I cleaned up the changelog significantly to make it more readable. My advice here is not to start with fixing tests. That is going to be frustrating and risks that things will be left broken. Instead, just read the changelog, and address each change one by one. A few may still remain, and only then would I start doing this in a test-driven way. The changelog of the C core is written manually, not automatically compiled from commits, so it should be relatively easy to follow. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
No, the changelog is here on the https://github.com/igraph/igraph/blob/develop/CHANGELOG.md Everything under the I am not saying NOT to look at tests, but that trying to do this in a test-driven way is a recipe for pain, frustration and maybe disaster. Not every change that is necessary will (or can) be caught by tests. I recommend using the changelog as the primary driver, and using tests to clean up what's left after. For example, if you rely on tests, you might notice strange behaviour from
|
Does this mean we should check the length of the unique values of the |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
It's the opposite: It means that this is no longer a concern. This is in the "Changed" section, which lists changes which are not really breaking. It's good to look at these, but the "Breaking changes" section is the more important one. I looked at the three bullet points under "Changed"—none of these need any adaptation from the R side. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Almost certainly. The build system we have is not that smart and may not handle switching between this branch and I should say that there's one type of change that is not in the changelog and is going to affect the R interface. This is parameter renamings done in So, parameter reorderings are documented, a these affect API compatibility in C. But parameter name changes are no documented, as these are not relevant in C. However, the names in |
When a function gained an argument in the C core, do we have to handle that or is there a default value anyway? |
|
I wonder whether we should also open "expose" issues for them to not forget. |
Absolutely. |
In many cases, the first and quickest step towards fixing things is to move functions to auto-generation. Kirill has done a lot of these already. That's why this branch even compiles. So, treat things from |
I am looking at the C docs to find the two new arguments to |
And with the drop-down, one does not get to the version of the same page, but instead to the homepage. 😭 |
Note: sometimes the CHANGELOG uses the word "argument" but other times it uses the word "parameter". |
@krlmlr @schochastics during the hackathon I suggest we look at #2097, editing the comments if needed. With a few example fixes it'd be easier for me to take over. |
7cbf490
to
a046f43
Compare
c704791
to
ff12872
Compare
@krlmlr Can you please update this to the latest |
To load the package I first have to delete the two cpp11 files. 🤨 There are two |
…onical_permutation_bliss()`
This shows the result of updating snapshot tests for the
next
branch. Also clearing the "embedding" and "games" tests.authority_score()
workshub_score()
workshits_score()
works -- authorityhits_scores()
works -- hubWe need to resolve this before vendoring on the
next
branch can resume.@szhorvat: Can you please help?