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

Sparse test sets #18844

Closed
wants to merge 9 commits into from
Closed

Sparse test sets #18844

wants to merge 9 commits into from

Conversation

lbollar
Copy link
Contributor

@lbollar lbollar commented Oct 8, 2016

Referencing #18801

Added testsets to all of sparse.jl test file. For tests clearly mentioning issues, I have tried to group them in an issues testset with each subset testset containing an individual issue.

@tkelman
Copy link
Contributor

tkelman commented Oct 8, 2016

On line 127, bitArray should be spelled BitArray

line 325 is still testing ctranspose

line 333 is still testing ftranspose!

line 488, leave the comment about sparse diff

line 781 and 874 and 1062 and 1281 and 1302 and 1395, getindex and setindex and dropstored! and sparse/sparsevec and spdiagm and similar are not capitalized

same on 1405, 1412, 1419, 1425, 1449, 1489, 1494, 1501, 1529, 1691 - don't capitalize function names

line 1167, don't put a testset around a function definition

line 1624, UniformScaling is the type name

don't delete the comments that describe what #12177 and #12118 and #18705 mean

@lbollar
Copy link
Contributor Author

lbollar commented Oct 8, 2016

Apologies, still learning the pull request process. I'm guessing I needed to have rebased my branch instead of merge committing. What is best way to handle this now that I have submitted pull request already?

@tkelman
Copy link
Contributor

tkelman commented Oct 8, 2016

I misread since github unhelpfully won't show a diff this big. It might have been better if split up into multiple commits of a few hundred lines each, but that's a consequence of bad tools. Viewing the diff as https://github.com/JuliaLang/julia/pull/18844/files?w=1 works better but @github won't let you leave review comments on that view.

The merge commit didn't hurt anything from what I can tell. You can address the review as additional commits to this branch in your fork, and we can squash upon merging.

@lbollar
Copy link
Contributor Author

lbollar commented Oct 8, 2016

I have all the changes ready but for these two comments:

line 325 is still testing ctranspose

line 333 is still testing ftranspose!

Do these mean that titles of test sets on these lines should mention these functions?

@tkelman
Copy link
Contributor

tkelman commented Oct 8, 2016

they do on master (the comments anyway). you changed the titles so they don't any more, which wasn't necessary

@kshyatt kshyatt added test This change adds or pertains to unit tests sparse Sparse arrays labels Oct 9, 2016
Base.SparseArrays.getindex_I_sorted_linear(A, I, J)
end

@testset "test_get_index_algs" begin
Copy link
Contributor

Choose a reason for hiding this comment

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

the function is called test_getindex_algs

Copy link
Contributor

Choose a reason for hiding this comment

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

I meant you should remove the underscore from get_index, not drop the test_ prefix

@tkelman
Copy link
Contributor

tkelman commented Oct 9, 2016

leave " for specialized matrix types" on line 1694

@tkelman
Copy link
Contributor

tkelman commented Oct 11, 2016

I pushed a minor revision to this branch. Note that lines 663-702 aren't related to issue #13024, and shouldn't be in the same testset.

@kshyatt
Copy link
Contributor

kshyatt commented Oct 13, 2016

@tkelman is this merge-able?

@tkelman
Copy link
Contributor

tkelman commented Oct 13, 2016

not until the "shouldn't be in the same testset" comment is addressed

@lbollar
Copy link
Contributor Author

lbollar commented Oct 13, 2016

Sorry, I misunderstood the meaning of your comment and thought you fixed this in your revision. I will take a look at this.

@lbollar
Copy link
Contributor Author

lbollar commented Oct 13, 2016

I am guessing I mistakenly assumed all sections were commented due to the excellent commenting in file. I didn't see comments in original for these blocks, so I attempted to name them myself. These are probably awful testset names, so feel free to correct.

@@ -738,6 +697,53 @@ end
end
end

@testset "Test equivalency of created identity matrices from sparse matrix" begin
Copy link
Contributor

Choose a reason for hiding this comment

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

best to check git blame and see when this was introduced to find the actual intent, instead of completely guessing

Copy link
Contributor

Choose a reason for hiding this comment

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

also best to put these back in the order in the file they were originally, so the diff is easier to review

@@ -661,6 +661,53 @@ end
end
end

@testset "spones" begin
Copy link
Contributor

Choose a reason for hiding this comment

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

this still isn't an "issue" - by original location I meant where they were in the file before your PR, not at an earlier commit

@lbollar
Copy link
Contributor Author

lbollar commented Oct 17, 2016

I moved them to after the first non issue related tests I could find in the original file where they took place. Sorry and thanks for patience.

@hayd
Copy link
Member

hayd commented Nov 13, 2016

bump! this needs a rebase.

@ViralBShah
Copy link
Member

@lbollar Would be great if you could rebase to master and we should get this merged asap. Thanks for the work and patience.

@lbollar
Copy link
Contributor Author

lbollar commented Nov 13, 2016

Traveling, but will try and get this done tonight when I get back home to
computer. Thanks for help.

@lbollar
Copy link
Contributor Author

lbollar commented Dec 8, 2016

I am sorry all. I became very busy. The merge conflicts created over time are more difficult to solve than just using the latest commit and what I have here as a guideline to redo everything. Most of this pull request thread has been spent discussing naming and organization, which is mostly complete now, so the rewrite shouldn't that be painful. After discussing with @kshyatt, I think this is best route. Semester is ending so I should be able to rewrite soon, hopefully looking at doing it this weekend. Sorry for the delay.

@lbollar lbollar closed this Dec 8, 2016
@ViralBShah
Copy link
Member

Thanks. Looking forward to having the new PR. Perhaps we should leave this one open in the meanwhile.

@lbollar lbollar mentioned this pull request Dec 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sparse Sparse arrays test This change adds or pertains to unit tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants