You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's entirely possible to get ARM data but no x86 data for a given timestamp -- for instance, CRuby might have an x86-specific crash, or there might be a rare crash that triggers by chance on x86 but not ARM. These things happen.
Right now, those timestamps get skipped. No ARM data shows up speed.yjit.org. That's an intentional thing, because the reporting code was all written x86-only initially, and some of it has bugs when trying to report with no x86 data present.
But it's not conceptually complicated. It just needs somebody to go through and fix the bugs with those reports.
The text was updated successfully, but these errors were encountered:
It's entirely possible to get ARM data but no x86 data for a given timestamp -- for instance, CRuby might have an x86-specific crash, or there might be a rare crash that triggers by chance on x86 but not ARM. These things happen.
Right now, those timestamps get skipped. No ARM data shows up speed.yjit.org. That's an intentional thing, because the reporting code was all written x86-only initially, and some of it has bugs when trying to report with no x86 data present.
But it's not conceptually complicated. It just needs somebody to go through and fix the bugs with those reports.
The text was updated successfully, but these errors were encountered: