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
Today, XHarness tests run after all the regular arcade tests finish. Frequently, the xharness tests timeout, despite the regular tests completing successfully, and you have to rerun the entire job (aka, all of the arcade tests + all the xharness tests). Xharness tests should be broken out into a separate job per configuration, so that when they need to be rerun, we don't have to rerun ALL of the tests (and possibly time out again).
The text was updated successfully, but these errors were encountered:
Oh, it looks like that when runtime is running the full BCL suite on the 10 iPhones we have and Arcade runs at the same time, they pile up on the few devices. I never noticed because runtime-staging rolling build only runs 2x a day and it's out of my hours.
Thanks for this @adiaaida. Can we now maybe prioritize #7979?
Today, XHarness tests run after all the regular arcade tests finish. Frequently, the xharness tests timeout, despite the regular tests completing successfully, and you have to rerun the entire job (aka, all of the arcade tests + all the xharness tests). Xharness tests should be broken out into a separate job per configuration, so that when they need to be rerun, we don't have to rerun ALL of the tests (and possibly time out again).
The text was updated successfully, but these errors were encountered: