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

Fixed BUG in findnz function for SparseMatrixCSR #264

Merged
merged 5 commits into from
May 23, 2020

Conversation

amartinhuertas
Copy link
Member

No description provided.

Copy link
Member

@fverdugo fverdugo left a comment

Choose a reason for hiding this comment

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

The build is failing. Can you fix it?

@amartinhuertas
Copy link
Member Author

The build is failing. Can you fix it?

Done in 5871c7c!

@codecov-commenter
Copy link

codecov-commenter commented May 23, 2020

Codecov Report

Merging #264 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #264   +/-   ##
=======================================
  Coverage   88.94%   88.94%           
=======================================
  Files         147      147           
  Lines        9604     9604           
=======================================
  Hits         8542     8542           
  Misses       1062     1062           
Impacted Files Coverage Δ
src/Algebra/SparseMatrixCSR.jl 76.92% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6dc2b7c...f534b0c. Read the comment docs.

@fverdugo fverdugo merged commit edd804b into master May 23, 2020
@fverdugo fverdugo deleted the fix_bug_in_sparsematrixcsr_findnz branch May 23, 2020 09:12
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.

3 participants