Skip to content

Fix tests/run.py stuck in macOS CI - #4410

Merged
zcbenz merged 1 commit into
mainfrom
fix-tests-run
Aug 26, 2026
Merged

Fix tests/run.py stuck in macOS CI#4410
zcbenz merged 1 commit into
mainfrom
fix-tests-run

Conversation

@zcbenz

@zcbenz zcbenz commented Aug 26, 2026

Copy link
Copy Markdown
Member

I'm out of idea why it is stuck in macOS CI and I can not reproduce locally :(
Switch back to python -m unittest discover -v python/tests for macOS CI for now before I figure out

@zcbenz
zcbenz requested a review from nastya236 August 26, 2026 10:29
@zcbenz zcbenz changed the title Fix tests/run.py stuck in CI Fix tests/run.py stuck in macOS CI Aug 26, 2026

@jagrit06 jagrit06 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yeah, lets revert for now

@zcbenz
zcbenz merged commit 7f2c431 into main Aug 26, 2026
82 checks passed
@zcbenz
zcbenz deleted the fix-tests-run branch August 26, 2026 12:57
@aleroot

aleroot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

This is a deadlock happening afterward because mx.clear_streams() holds the GIL while synchronously waiting for Metal callbacks that may need the GIL to release Python-owned DLPack data. Changing unittest invocation or runner size only masks the timing bug... I cannot even open a PR because now max one PR at a time...

@zcbenz

zcbenz commented Aug 26, 2026

Copy link
Copy Markdown
Member Author

@aleroot Thanks for looking into this and sorry for the inconvenience, you should be able to open the new PR as a draft, or make the currently open one draft before opening a new one. We added some rules to avoid getting flooded by PRs.

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