Skip to content

Remove hardcoded posix semaphore value - #1315

Merged
Simn merged 1 commit into
HaxeFoundation:masterfrom
Aidan63:fix-hardcoded-semaphore-value
Mar 8, 2026
Merged

Remove hardcoded posix semaphore value#1315
Simn merged 1 commit into
HaxeFoundation:masterfrom
Aidan63:fix-hardcoded-semaphore-value

Conversation

@Aidan63

@Aidan63 Aidan63 commented Mar 8, 2026

Copy link
Copy Markdown
Contributor

Forgot I changed this while debugging an issue...

Forgot I changed this during debugging
@Simn
Simn merged commit 2ce4afa into HaxeFoundation:master Mar 8, 2026
133 checks passed
@Simn

Simn commented Mar 8, 2026

Copy link
Copy Markdown
Member

https://xkcd.com/221/

@Aidan63
Aidan63 deleted the fix-hardcoded-semaphore-value branch March 8, 2026 18:43
@Simn

Simn commented Mar 8, 2026

Copy link
Copy Markdown
Member

I'm seeing this in the Haxe threads tests now:

results: SOME TESTS FAILURES (success: false)
cases.TestSemaphore
  test: ERROR ..E
    Failed to wait for semaphore

@Aidan63

Aidan63 commented Mar 8, 2026

Copy link
Copy Markdown
Contributor Author

I'm now playing around with getting the haxe side to use the typed object and have started getting failing semaphore tests (tryAcquire returning true when it should be false), so something odd is going on.

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