MobileFrontend Builds [1] 536-592 have failed. That's a lot.
Does anyone care about this job?
Should we disassemble it into smaller jobs just like we did with smoke tests [2]?
That said even our smaller smoke test job has been problematic (Chris mentioned an issue with the latest chrome driver but that was a month ago and I don't know where the bug for this is).
These browser tests are useless if no one is watching them and/or they are spinning out false positives and I can't be the only one to complain when these tests break. This should be a shared responsibility.
These are not new issues and they continue to frustrate me.