Looks like guado-paladin has failed consistently for the last 10 runs due to failure in webrtc_PausePlayPeerConnections (like this one: https://stainless.corp.google.com/browse/chromeos-autotest-results/227032059-chromeos-test/ "Devtools target crashed"). This seems to be an existing known problem (see b:79153430) and the "solution" seems to have been to add RETRIES = 2 to the affected tests. Looks like that's not enough retries anymore, or there's a more permanent problem. Can you guys please take a look, and increase the RETRIES further if necessary?
Also, Ege, is this paladin still supposed to be experimental? There doesn't seem to be much justification on why this was moved in the first place in https://crosreview.com/862997. I assume it was done while adding new possibly flaky CfM-specific hardware tests... but it has been half a year now and as far as I know(?) this device is also used as a non-CfM Chromebox. We're not going to keep those users without test coverage forever just to support the CfM use of the platform, are we?
Comment 1 by kerl@google.com
, Aug 28