On 19/07/2019 17:55, Severin Gehwolf wrote:
:
My issue is with finding those tests :-/ If we know the set of *all*
tests affected by the breakage we could do approach 2. Approach 1 (or
3) seems safer.
Any impact will be limited to tests using the test infrastructure but using their own policy. I agree #1 or #3 is the safest.

I just scanned the new webrev (02/webrev) and it looks good to me.

-Alan

Reply via email to