239825 2022-04-27 13:46:24 -0700 We should not stop running EWS with merge-blocked label if it is put by the same EWS test 2022-05-18 13:57:38 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 240169 InRadar P2 Normal --- 239082 1 ysuzuki webkit-unassigned webkit-bug-importer oldest_to_newest 1864918 0 ysuzuki 2022-04-27 13:46:24 -0700 We would like to collect failures with one set of EWS run as much as possible. Once one of test puts merge-blocked label, then the other EWS tasks in the same set of EWS stops, which enforces us to upload a patch repeatedly to collect failures on each platform, which is not efficient and regression from the current form of EWS. 1864961 1 ysuzuki 2022-04-27 15:49:56 -0700 I'm now getting it in https://github.com/WebKit/WebKit/pull/420 too, which EWS tests are blocked by mips compilation failure. 1864964 2 ysuzuki 2022-04-27 15:55:31 -0700 I think merge-blocked label should not affect on EWS test runs since we didn't have such a thing in bugzilla. We can stop EWS if a new change is pushed in PR (as we did in bugzilla), but if it is not, I don't think we should stop EWS testings. 1866582 3 webkit-bug-importer 2022-05-04 13:47:13 -0700 <rdar://problem/92752163> 1870141 4 ryanhaddad 2022-05-18 13:57:38 -0700 Apologies for the forward dupe, this has been fixed. *** This bug has been marked as a duplicate of bug 240169 ***