> Can we fix wpt-sync to work in a before/after mode instead of depending on mozilla-central? Yes, probably but that's additional complexity that we don't already have. > We do not have the luxury of running unlimited tests because they exist, if there are some subsets of non expected-pass tests that we need to run, I would like them to be justified individually with a business case: Given that "expected pass" as defined here doesn't map logically onto the semantics you want, I don't think that's a reasonable position to take. I have proposed an alternative solution (deprioritise tests for features we've made a business decision not to support). I think it's reasonable to have a discussion about the different tradeoffs, but I don't think it's reasonable to start from the assumption that the proposal in comment #0 is the correct solution.
Bug 1572820 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Can we fix wpt-sync to work in a before/after mode instead of depending on mozilla-central? Yes, probably but that's additional complexity that we don't already have. > We do not have the luxury of running unlimited tests because they exist, if there are some subsets of non expected-pass tests that we need to run, I would like them to be justified individually with a business case: Given that "expected pass" as defined here doesn't map logically onto the semantics you want, I don't think that's a reasonable position to take. I have proposed an alternative solution (deprioritise tests for features we've made a business decision not to support). I think it's reasonable to have a discussion about the different tradeoffs, but I don't think it's reasonable to start from the assumption that the proposal in comment #0 is the correct solution.