In this Try I ended up using `system_profiler` and `xrander` for mac/linux respectively https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&author=kshampur%40mozilla.com&selectedTaskRun=bUsgVdnqS9uLtMEpzXGdBw.0 it seems the M2 machines are 60hz, and the linux machines are 60 hz( actually ~59.87 but should satisfy the 60 hz criteria) just waiting on the 10.15 machines to start running. If that is also 60hz I will close this. Potentially file a follow up bug of having a unit test verify the refresh rates in raptor tests. But seems like a nice to have at this point
Bug 1917594 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In this Try I ended up using `system_profiler` and `xrander` for mac/linux respectively https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&author=kshampur%40mozilla.com&selectedTaskRun=bUsgVdnqS9uLtMEpzXGdBw.0 it seems the M2 machines are 60hz, and the linux machines are 60 hz( actually ~59.87 but should satisfy the 60 hz criteria) just waiting on the 10.15 machines to start running. If that is also 60hz I will close this. Potentially file a follow up bug of having a unit test verify the refresh rates in raptor tests, for mac/linux. But seems like a nice to have at this point