-
Notifications
You must be signed in to change notification settings - Fork 527
chore: Add macos executor for unit tests
#1334
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.
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
Conversation
…o _worker_task_orchestrator loop being too intensive?
33ba628 to
ea070ff
Compare
ea070ff to
2e85e3b
Compare
|
MacOS executors sometimes start with CPU usage of 100 % even before starting the test. |
1e1e4ce to
4dc65b9
Compare
4dc65b9 to
48830c3
Compare
|
Looks like the Spotlight service on the executor can randomly start and use all the CPU. We should probably just turn it off on the executor, this service is completely useless in our context. |
2056d9e to
f4a00c2
Compare
f4a00c2 to
4435c8a
Compare
3be1bb5 to
58c8140
Compare
|
Executor related changes made |
4ca8452 to
19e820a
Compare
19e820a to
fc0632f
Compare
vdusek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
MacOSto prevent OS-specific incompatible changes, for example: Memory estimation problem on MacOS #1329test_emit_system_info_eventto minimize flakiness of the test.