Skip to content

Put FINUFFT back to choosing its own threads after a one-thread test - #151

Merged
mcencini merged 1 commit into
mainfrom
claude/project-thread-em6q4x
Oct 14, 2026
Merged

mcencini merged 1 commit into
mainfrom
claude/project-thread-em6q4x

Conversation

@mcencini

Copy link
Copy Markdown
Collaborator

Requested by Matteo · project thread

Before: the v0.0.16 wheel builds (publish.yml) failed on every platform at test_one_thread_count_covers_bart_and_the_transform (assert 4 == 0). The _one_thread fixture added in #150 resets BART's thread count after its test but leaves FINUFFT on that count, and the wheel tests run every file serially in one process.

After: the fixture also calls _finufft.set_threads(0), which puts FINUFFT back to choosing its own count. The test change is one line, and no library code changes.

How: I reproduced the failure locally by running the two tests in order in one process (1 failed). With the fix, both pass. tests/test_apps.py and tests/test_finufft.py run serially give 195 passed and 25 skipped. Lint is clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MscKdxsmwEWWNpur8CU8hR


Generated by Claude Code

The one-thread fixture restored BART's count but left FINUFFT on it, so
test_one_thread_count_covers_bart_and_the_transform, run later in the same
process as the wheel tests do, found 4 where it expects 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MscKdxsmwEWWNpur8CU8hR
@codecov

codecov Bot commented Oct 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mcencini
mcencini merged commit 308ef6a into main Oct 14, 2026
14 checks passed
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.

2 participants