tree 398881aeb946f1389920238379ac1b3448d5ea00
parent dad30a80f4847ef7676fa20b078413ab36977eec
author moz-wptsync-bot <wptsync@mozilla.com> 1605727417 +0000
committer GitHub <noreply@github.com> 1605727417 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJftXS5CRBK7hj4Ov3rIwAAdHIIABe8AqANKoJSKiad2RSgjroJ
 feW6d5ViFZSczE9khZyf66zXEK+J4kmo0hAvCPgwHFwk2JdriW4L9Q+GxyFY8k+t
 +90W8WAvbkd3QgDjJgXT5DllvLOC+5tti1wuJ1tJYZR3rzvvJaeHPequeixGcSWP
 kY5xbuzc53A0/1y8FRFFiytJwxcrR7Tij8CF8RgjX2jyKkX9p9rZfVA4xhRJ5NW0
 N2NryTBQIfkuHFEhF3vjABQ3X4Kr7acj6EBBhF3muPHYjchYG5Qee2dMHN/mm82L
 j/5GSd5VsrWnZgtQpofAf0xNsXFK3xg/w7VmnPKb39Kx9qfzWq3i0s40PmRIt04=
 =koUw
 -----END PGP SIGNATURE-----
 

Don't change wpt metadata when new metadata is a subset of old (#26508)

We often see metadata changes like [PASS, FAIL] going to [FAIL,
PASS]. Although in principle we'd like the most common status to be
first, when we have things like expected: [PASS, FAIL] getting lots of
os-specific expectations because the frequency is different on
different platforms it doesn't help much.

Instead, if the new metadata is a subset of the old, bail early and
don't make any changes.

Differential Revision: https://phabricator.services.mozilla.com/D96750

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1676717
gecko-commit: 26618d9cd273b51b6f80912b932177b65c983baf
gecko-reviewers: karlcow, denschub

Co-authored-by: James Graham <james@hoppipolla.co.uk>