ci: Add doctests to CI again.

[hameerabbasi]

What type of PR is this? (check all applicable)

• 💾 Refactor
• 🪄 Feature
• 🐞 Bug Fix
• 🔧 Optimization
• 📚 Documentation
• 🧪 Test
• 🛠️ Other

Related issues

• Related issue #
• Closes #

Checklist

• Code follows style guide
• Tests added
• Documented the changes

---

Please explain your changes below.

[codspeed-hq]

CodSpeed Performance Report

Merging #767 will degrade performances by 41.43%

_{Comparing hameerabbasi:doctests-2 (e86fc3a) with main (b4ba7c6)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 338 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	hameerabbasi:doctests-2	Change
⚡	test_index_fancy[side=100-rank=1-format='coo']	1,242.2 µs	642.4 µs	+93.36%
❌	test_index_slice[side=100-rank=2-format='gcxs']	2.4 ms	4.1 ms	-41.43%

[hameerabbasi]

@willow-ahrens Doctest issue.

[willow-ahrens]

using numba from the numba channel (with a statically linked llvmlite) fixes the segfault issue on mac. It appears that the segfault issue is mac-only at this point, as linux supports some special symbol resolution thing that fixed this problem.

Proposed solution: I would like to leave a warning to users on startup in the event that they have tried to load this particular config of packages. I think we could warn in pydata/sparse whenever we see (conda in use) AND (macos) AND (numba was not installed from numba channel)

As a side note: it is odd to me that we are loading both numba and finch at the same time. we might reduce some of this headache by switching between backends as a build option, rather than a runtime option.

[willow-ahrens]

I cannot get a reproducer for this in docker, though I have tried. If anyone can get a reproducer for this that would be great, then we can put it in an issue where we describe the problem. If you ssh into the CI runner, even doing "import sparse.finch_backend" will segfault, so we don't need all the pytest stuff to reproduce.

[willow-ahrens]

I've put a comment in to pyjuliapackage that we experience an issue with parallel installs, and suggested a fix here: JuliaPy/pyjuliapkg#19

[willow-ahrens]

also, note this comment regarding installation of juliacall and numba on conda: JuliaPy/PythonCall.jl#215 (comment)

[mtsokol]

LGTM! Just one question.

[mtsokol]

And please remember about a commit squash!