Bug 239825 - We should not stop running EWS with merge-blocked label if it is put by the same EWS test
Summary: We should not stop running EWS with merge-blocked label if it is put by the s...
Status: RESOLVED DUPLICATE of bug 240169
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks: 239082
  Show dependency tree / graph
 
Reported: 2022-04-27 13:46 PDT by Yusuke Suzuki
Modified: 2022-05-18 13:57 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yusuke Suzuki 2022-04-27 13:46:24 PDT 
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.
Comment 1 Yusuke Suzuki 2022-04-27 15:49:56 PDT 
I'm now getting it in https://github.com/WebKit/WebKit/pull/420 too, which EWS tests are blocked by mips compilation failure.
Comment 2 Yusuke Suzuki 2022-04-27 15:55:31 PDT 
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.
Comment 3 Radar WebKit Bug Importer 2022-05-04 13:47:13 PDT 
<rdar://problem/92752163>
Comment 4 Ryan Haddad 2022-05-18 13:57:38 PDT 
Apologies for the forward dupe, this has been fixed.

*** This bug has been marked as a duplicate of bug 240169 ***