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.

Sign up for GitHub

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

Jump to bottom

[macOS] TestConcurrentSignalWatchBreak.py fails spuriously #39394

Closed
martong opened this issue Dec 17, 2018 · 2 comments
Closed

[macOS] TestConcurrentSignalWatchBreak.py fails spuriously #39394

martong opened this issue Dec 17, 2018 · 2 comments
Labels
bugzilla Issues migrated from bugzilla lldb

Comments

@martong
Copy link
Collaborator

martong commented Dec 17, 2018

Bugzilla Link 40047
Version unspecified
OS Linux
Attachments output of test execution
CC @Teemperor

Extended Description

Executing 'ninja check-lldb' produced a fail in TestConcurrentSignalWatchBreak.py.

However, when I executed the test with './bin/lldb-dotest -p TestConcurrentSignalWatchBreak.py' the test passed. So, this test sometimes fail, sometimes pass. I suspect some thread synchronization issue or a wait/poll problem here.
@Teemperor
Copy link
Collaborator

Can you write how many jobs ninja is using on your machine? This helps with reproducing.

@martong
Copy link
Collaborator Author

martong commented Dec 17, 2018

Sure, it is 10. I use ninja's default, which is 10 on this macBook:
-j N run N jobs in parallel [default=10, derived from CPUs available]

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@martong martong closed this as completed Apr 26, 2022
@ilovepi ilovepi mentioned this issue Oct 8, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla lldb
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Teemperor @martong